ResolutionRelay API Search

Server Details

Search millions of x402 APIs for data, finance, validation, security, inventory, sync and automation

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-07 00:41
Transport: Streamable HTTP
URL

TDQS

A4.1/5.0

Disambiguation4/5

Each tool has a clear role: get_api retrieves by slug, list_apis pages all inventory, search_apis does natural-language discovery, and prepare_api_execution sets up payment. Search and list are related but descriptions distinguish their use cases well. Minor ambiguity exists between get_api and list_apis for simple retrieval, but slug-based lookup clarifies the boundary.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_api, list_apis, search_apis, prepare_api_execution. Naming is predictable and clearly indicates the action taken.

Tool Count5/5

Four tools is well-scoped for an API discovery and execution preparation server. Each tool represents a distinct step in the workflow: discover, retrieve, search, and prepare.

Completeness4/5

The server covers the core consumer workflow: finding APIs via search/list/get and preparing paid executions. The actual execution call is deliberately externalized behind the payment gate, so no tool is strictly missing. A minor gap is the lack of a direct search refinement or pagination control, but it is not essential.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesAug 19, 2026
- Removedcatalog_stats
- Addedlist_apis
- Addedprepare_api_execution
- Changedsearch_apis6 fields changed
  - addedInput schema / properties / cursor
```
Added value: +{
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
  - changedInput schema / properties / limit / default
```
Previous value: -8New value: +10
```
  - removedInput schema / properties / limit / description
```
Removed value: -"Maximum matches to return."
```
  - changedInput schema / properties / limit / maximum
```
Previous value: -20New value: +50
```
  - changedInput schema / properties / query / description
```
Previous value: -"Natural-language capability needed, e.g. validate invoice totals or detect duplicate records."New value: +"What capability or business outcome is needed"
```
  - removedInput schema / properties / query / maxLength
```
Removed value: -500
```
3 tool updatesAug 19, 2026
- First observedcatalog_stats
- First observedget_api
- First observedsearch_apis

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

EntRoute A
com.entroute
Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price.
Developer Tools Payments & Billing
321
graded-x402 B
sh.graded
Discover and call 2,000+ x402 machine-payable services through one graded API key + gateway.
Payments & Billing Developer Tools
1
AgentIndex
io.github.agentndx
Search 15K+ MCP services, A2A agents, and x402 APIs from 5 registries. Paid via x402 (USDC on Base).
Search Agent Orchestration
2
HelpMyAgent A
io.github.helpmyagent
Pay-per-call data APIs for AI agents: business, compliance, procurement, VAT and IBAN via x402.
Cryptocurrency Payments & Billing Data Platforms
481

Related MCP Servers

x402search
Search Blockchain Web3 & Decentralized Tech
x402-index
A
license
A
quality
D
maintenance
Search 14,000+ x402-enabled HTTP APIs by keyword. Agents pay $0.01 USDC per search via x402 micropayments on Base mainnet — no API keys or accounts required.
Updated 5 months ago (2026-03-29 07:38 UTC)
1
39
2
MIT
AfaAgent x402 API Suiteofficial
Blockchain AI & Machine Learning Developer Tools
AfaAgent
F
license
Not graded
quality
C
maintenance
43 x402-enabled API tools — DeFi, wallet security, AI/ML, developer tools, SEO. Pay-per-call USDC on Base via x402 protocol.
Updated a month ago (2026-07-27 00:36 UTC)
-
nohumans-mcp
Search Monitoring Payments & Billing
jalcodev
F
license
Not graded
quality
B
maintenance
Find and vet paid x402 API services before an agent spends money on them, with live reliability scores and recency-weighted probing.
Updated 8 days ago (2026-08-31 18:45 UTC)
-
Orbis MCPofficial
Agent Orchestration Web3 & Decentralized Tech Cryptocurrency
OrbisAPI
A
license
Not graded
quality
F
maintenance
Connects AI agents to 2,800+ APIs via x402 micropayments on Base, enabling automated API calls for $0.01 each without signup or API keys.
Updated 3 months ago (2026-06-11 15:17 UTC)
95
2
MIT