ai.edge-agents/intelligence
REMOTE · PAY.EDGE-AGENTS.AI
Macro, market and decision intelligence over x402. Gaps are unavailable rather than estimated.
Available components
Last scanned (3 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 774 tokens (~96/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- Schema quality: 635 → 774 ▼ functional
- New tool “edge_ask” functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 15 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://pay.edge-agents.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pay.edge-agents.ai | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 22b9b32a7b7581100e7a9bda90773729 |
| SANs: pay.edge-agents.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pay.edge-agents.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| edge-agents.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pay.edge-agents.ai/mcp | Verified | 200 | |
| http (plaintext) | http://pay.edge-agents.ai/mcp | HTTPS enforced | 301 | https://pay.edge-agents.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edge_ask Ask a question, get the services to buy ~139
Describe what you want to know in plain language and get back the services worth buying, with price, endpoint, free-sample link and the keywords that matched. A question with several parts, for example 'btc leverage and eurozone inflation', is split into topics and routed separately, and the picks are bundled with a total price. Routing only: nothing is called or purchased, and it matches keywords rather than interpreting the question. Start here when you do not yet know which services you need.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Your question or need in plain language, up to 300 characters, for example 'what can move bitcoin next, and when'. |
No output schema declared.
No examples provided.
edge_get_free_sample Get a free illustrative sample ~67
Fetch a free, illustrative sample of a service's output so the response shape and evidence style can be inspected before paying. The sample is illustrative: treat it as a schema and quality guide, not as current market evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | The service id to sample. |
No output schema declared.
No examples provided.
edge_get_report_terms Get a report's live payment terms (x402) ~104
Read the live x402 payment terms for a service's report: the price, and one offer per settlement rail, exactly as the paid endpoint issues them. Use this to check a report's cost against your own spend policy before committing. Settlement happens over the plain HTTP endpoint named in the response, not through this tool -- signing a payment needs your own wallet, which no MCP client holds.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | The service id whose payment terms you want. |
No output schema declared.
No examples provided.
edge_get_service Get a service's full record ~93
Look up one service by its id and return its full public record: what it produces, its price, its freshness target, its output schema version and its purchase endpoint. Call this before purchasing so the price and freshness are known rather than assumed. The top result is the exact id match.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | The service id, as returned by edge_search_services or a product bundle's sample.serviceId. |
No output schema declared.
No examples provided.
edge_list_families List service families ~53
List the families the catalogue is organised into, with a service count for each. Use this to browse when a keyword search is too narrow, or to check coverage of a subject area before committing to a purchase.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_products List the buyer-facing product bundles ~52
List the packaged products, each of which composes several specialist services into one buyer outcome, with its free sample and its representative purchase path. Prefer these over assembling specialist services yourself when a product already matches the question.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_search_services Search the intelligence catalogue ~83
Find intelligence services by keyword. Returns id, name, description, family and price for each match. Start here when you know what evidence you need but not which service provides it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results to return (default 25). |
| query | string | yes | Free-text search, for example 'bitcoin leverage' or 'eurozone inflation'. |
No output schema declared.
No examples provided.
edge_service_health Check service availability and freshness ~99
Report per-service availability and data freshness. Call this when a purchase matters and staleness would change the decision: a service can be operational but working from evidence older than its freshness target, which is reported rather than hidden. Omit serviceId for the platform summary; pass one for a single service's probe record.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | – | Optional. A single service's id, for its own probe record instead of the platform summary. |
No output schema declared.
No examples provided.
How do I install the ai.edge-agents/intelligence MCP server?
ai.edge-agents/intelligence is a hosted endpoint at https://pay.edge-agents.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pay.edge-agents.ai
claude mcp add --transport http ai-edge-agents-intelligence 'https://pay.edge-agents.ai/mcp'
What is the ai.edge-agents/intelligence MCP server?
ai.edge-agents/intelligence is an MCP server listed in the public MCP registry as ai.edge-agents/intelligence. Macro, market and decision intelligence over x402. Gaps are unavailable rather than estimated. This page covers its hosted endpoint (https://pay.edge-agents.ai/mcp).
Is the ai.edge-agents/intelligence MCP server safe to use?
ai.edge-agents/intelligence scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.edge-agents/intelligence MCP server expose?
ai.edge-agents/intelligence exposes 8 tools: edge_ask, edge_search_services, edge_list_families, edge_get_service, edge_get_free_sample, and 3 more. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.
Does the ai.edge-agents/intelligence MCP server require authentication?
No. We connected to ai.edge-agents/intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.edge-agents/intelligence MCP server still maintained?
ai.edge-agents/intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.