Rahuldsarker API Verified

{
  "service_type": "platform",
  "base_url": "https://rahuldsarker.co",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "model": "free",
      "currency": "USD",
      "free_tier": "Free Plan",
      "starting_at": "",
      "notes": "No signup, no API key required"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "MCP server over streamable HTTP",
    "No signup, no API key required",
    "111 marketing, RevOps and SaaS finance calculators",
    "Article and case study search with citable links",
    "Live call availability in the caller's time zone",
    "All tools read-only",
    "Listed in the Official MCP Registry"
  ],
  "raw_analysis": "Rahuldsarker API is a free public MCP (Model Context Protocol) server hosted at https://rahuldsarker.co. It is not a conventional REST API — instead it exposes tools over streamable HTTP for MCP-compatible clients. No authentication is required: no API key, no signup.\n\nWhat it does: The server provides 111 calculators covering marketing, RevOps, and SaaS finance (ROAS, break-even ROAS, LTV:CAC, CAC payback, SaaS valuation multiples from ARR/growth/NRR/margin). It also offers search over articles and case studies (fractional CMO, attribution, RevOps) with links intended for citation, and live call booking availability resolved to the caller's time zone.\n\nWho it's for: Startup founders, marketing and RevOps teams, SaaS finance teams, D2C brands, and AI agents performing marketing/finance analysis.\n\nMaturity: Early-stage, personal/solo-vendor project (author personal site). Discoverability is via the Official MCP Registry and direct URL. All tools are read-only, which keeps the integration low-risk. There is no explicit public REST surface documented, so no discrete endpoints are enumerated here.\n\nIntegrations: Works with any MCP client, including Claude, Cursor, VS Code, and ChatGPT. Listed alternatives are web calculators (Omni Calculator, HubSpot marketing calculators, Calculator.net), suggesting positioning as an agent-consumable calculator layer rather than a full platform.\n\nPricing: Free. No paid tier indicated.\n\nRate limits: Not documented.\n\nBecause this is an MCP server rather than a REST API, consumers should integrate through an MCP client using the streamable HTTP transport at the platform base URL."
}

3/3 tests passed

{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 9.5,
    "response_parseability": 8.5,
    "error_clarity": 7.5,
    "doc_quality": 7.5,
    "auth_simplicity": 10.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "free",
    "currency": "USD",
    "free_tier": true,
    "starting_at": 0,
    "notes": "No signup, no API key, no cost"
  },
  "issues": [
    "No structured OpenAPI schema surfaced in checks — parseability relies on MCP tool definitions rather than a discoverable spec in the analyzed data",
    "llms.txt describes an individual (Rahul D Sarker) rather than the tool platform's capabilities, reducing doc_quality for agents trying to reason about the MCP server",
    "Error handling behavior (invalid inputs, rate limits, empty result sets) not evidenced in the check results",
    "No status page or uptime history referenced, so consistency scoring is inferred from a single successful 200 response"
  ],
  "recommendations": [
    "Publish an llms.txt (or add a section) that enumerates the 111 calculators and MCP tool signatures so agents can plan calls without trial-and-error",
    "Expose a machine-readable tool manifest (JSON schema) at a stable URL to boost parseability and first-try success",
    "Document error shapes and limits (rate caps, max query length, unsupported calculator IDs) to improve error_clarity",
    "Link a status/uptime page to substantiate consistency claims",
    "Keep the no-auth, read-only model — it's the platform's strongest agent-friendliness signal"
  ]
}