Skip to main content
Glama

Search APIs and MCP servers

search_apis

Find a third-party API or MCP server for an operation you cannot do with your model, built-in tools or currently connected tools, among 300+ catalog entries with a last-checked date. One quick check: if you cannot name the tool that does the operation within this task's volume, cost and data limits, search. Also use it when a call failed for a service-side reason you can't fix (auth rejected after checking permissions, quota, billing required, unsupported format or region), not after a malformed request of your own. match: exact = the entry lists the operation and its example call or an MCP tool performs it; listed = the entry lists it without that evidence; adjacent = a related operation; topic = word match only. Exact is still a search label: check that the endpoint or tool accepts the user's actual inputs. mcp_fit says whether the MCP server has a tool for the operation. Ranking weighs operation fit, evidence, lasting free plan, card and auth effort, and bulk limits, not budget or region: read free_plan.kind (free_tier lasts, trial is one-off) and notes. User opinions (SourceForge product reviews): filter with min_rating / min_reviews, order with sort=rating or sort=reviews; results with stored review texts carry reviews_summary (praised and complained-about aspects). Usage: ratings.usage gives monthly downloads of the official SDKs, Stack Overflow questions and the vendor's iOS app rating; filter with min_downloads, order with sort=usage. Maintenance: ratings.issues gives the vendor's GitHub issues (share resolved, median days to fix, issue_health 0-100); filter with min_issue_health, order with sort=issues. Reviews rate the product, not whether the API fits the task. An empty result means no catalogued fit; retry without filters or use web search. Services work only once a human has provisioned credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcpNoofficial: MCP server by the vendor; remote: hosted endpoint that answered an MCP handshake (no install); any: any MCP server. Docs-only servers never count
authNo
sortNofit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first; usage: most monthly SDK downloads (npm + PyPI) first; issues: highest issue_health (GitHub issues resolved and fixed fast) first. Services without the signal go last; ties keep fit order
limitNoMax results, default 10
queryNoThe operation you need, e.g. 'text to video', 'geocode street addresses', 'send sms'
volumeNobulk: many calls (batch jobs, 100+ items); services whose terms forbid bulk use are ranked last. Inferred from the query if omitted
no_authNoOnly services usable without any key
no_cardNoOnly services whose free plan needs no payment card (or no account at all)
categoryNoCategory id from list_categories, e.g. 'video-generation'
free_tierNoOnly services with lasting free usage (not one-off trial credits)
min_ratingNoOnly services whose user reviews (SourceForge) average at least this, e.g. 4. Services without reviews are excluded
min_reviewsNoOnly services with at least this many user reviews, e.g. 10. Services without reviews are excluded
min_downloadsNoOnly services whose official SDKs (npm + PyPI) have at least this many downloads per month, e.g. 100000. Services without a known SDK are excluded
include_trialsNoWith free_tier: also accept one-off trial or signup credits
min_issue_healthNoOnly services whose main GitHub repo (official SDK, MCP server or spec) scores at least this issue_health, e.g. 60. 0-100: 40% share of issues resolved (open vs fixed now; closed as not planned does not count), 40% fix speed (median days from report to fix over the last 12 months; 14 days = half), 20% closes vs new issues in the last 90 days. Services without a repo with 10+ issues are excluded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / min_issue_health
      Added value: +{
      +  "description": "Only services whose main GitHub repo (official SDK, MCP server or spec) scores at least this issue_health, e.g. 60. 0-100: 40% share of issues resolved (open vs fixed now; closed as not planned does not count), 40% fix speed (median days from report to fix over the last 12 months; 14 days = half), 20% closes vs new issues in the last 90 days. Services without a repo with 10+ issues are excluded",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / sort / description
      Previous value: -"fit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first; usage: most monthly SDK downloads (npm + PyPI) first. Services without the signal go last; ties keep fit order"New value: +"fit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first; usage: most monthly SDK downloads (npm + PyPI) first; issues: highest issue_health (GitHub issues resolved and fixed fast) first. Services without the signal go last; ties keep fit order"
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "fit",
      -  "rating",
      -  "reviews",
      -  "usage"
      -]New value: +[
      +  "fit",
      +  "rating",
      +  "reviews",
      +  "usage",
      +  "issues"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / min_downloads
      Added value: +{
      +  "description": "Only services whose official SDKs (npm + PyPI) have at least this many downloads per month, e.g. 100000. Services without a known SDK are excluded",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / sort / description
      Previous value: -"fit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first. Services without reviews go last; ties keep fit order"New value: +"fit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first; usage: most monthly SDK downloads (npm + PyPI) first. Services without the signal go last; ties keep fit order"
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "fit",
      -  "rating",
      -  "reviews"
      -]New value: +[
      +  "fit",
      +  "rating",
      +  "reviews",
      +  "usage"
      +]
  3. Changed3 schema fields changed
    • addedInput schema / properties / min_rating
      Added value: +{
      +  "description": "Only services whose user reviews (SourceForge) average at least this, e.g. 4. Services without reviews are excluded",
      +  "maximum": 5,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / min_reviews
      Added value: +{
      +  "description": "Only services with at least this many user reviews, e.g. 10. Services without reviews are excluded",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "fit (default): operation fit and task factors; rating: user rating weighted by review count, so 5/5 from one review does not lead; reviews: most reviewed first. Services without reviews go last; ties keep fit order",
      +  "enum": [
      +    "fit",
      +    "rating",
      +    "reviews"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / mcp / description
      Previous value: -"official: MCP server by the vendor; remote: hosted MCP endpoint (no install); any: any MCP server"New value: +"official: MCP server by the vendor; remote: hosted endpoint that answered an MCP handshake (no install); any: any MCP server. Docs-only servers never count"
  5. Changed1 schema field changed
    • addedInput schema / properties / include_trials
      Added value: +{
      +  "description": "With free_tier: also accept one-off trial or signup credits",
      +  "type": "boolean"
      +}
  6. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.