io.github.goodmeta/intelligence-mcp
REMOTE · INTEL.GOODMETA.CO · 2 COMPONENTS · SCANNED SEP 28
Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP.
Available components
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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 463 tokens (~115/item across 4 items; 3 tools + 1 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.goodmeta/intelligence-mcp server?
io.github.goodmeta/intelligence-mcp is a hosted endpoint at https://intel.goodmeta.co/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 · intel.goodmeta.co
claude mcp add --transport http goodmeta-intelligence-mcp 'https://intel.goodmeta.co/mcp'
{
"mcpServers": {
"goodmeta-intelligence-mcp": {
"url": "https://intel.goodmeta.co/mcp"
}
}
} {
"servers": {
"goodmeta-intelligence-mcp": {
"type": "http",
"url": "https://intel.goodmeta.co/mcp"
}
}
} [mcp_servers.goodmeta-intelligence-mcp] url = "https://intel.goodmeta.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"goodmeta-intelligence-mcp": {
"type": "remote",
"url": "https://intel.goodmeta.co/mcp",
"enabled": true
}
}
} openclaw mcp add goodmeta-intelligence-mcp --url 'https://intel.goodmeta.co/mcp' --transport streamable-http
mcp_servers:
goodmeta-intelligence-mcp:
url: "https://intel.goodmeta.co/mcp" {
"McpServers": {
"goodmeta-intelligence-mcp": {
"Transport": "http",
"Url": "https://intel.goodmeta.co/mcp"
}
}
} assistant mcp add goodmeta-intelligence-mcp -t streamable-http -u 'https://intel.goodmeta.co/mcp'
{
"mcpServers": {
"goodmeta-intelligence-mcp": {
"type": "http",
"url": "https://intel.goodmeta.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- 19 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 16 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- 15 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 9 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- 8 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool “scan_opportunities” rewrote its description, which is the text the model reads security
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 28 Sept 2026 · Probed https://intel.goodmeta.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=intel.goodmeta.co | CN=YE1,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6b3bd0506544a425876cd0eb72dc54a1acd |
| SANs: intel.goodmeta.co | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of intel.goodmeta.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| goodmeta.co. | 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://intel.goodmeta.co/mcp | Verified | 200 | |
| http (plaintext) | http://intel.goodmeta.co/mcp | HTTPS enforced | 301 | https://intel.goodmeta.co/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 →
compare_protocols Compare Protocols ~108
Get a side-by-side comparison matrix of all five agent payment protocols (AP2, ACP, x402, MPP, UCP) across creator, layer, agent delegation, budget limits, cross-merchant coordination, and MCP integration. Use when the user asks to compare protocols ('AP2 vs ACP', 'which protocol handles budgets?', 'what's the difference between x402 and MPP?', 'show me the landscape'). Use get_protocol_info instead for deep details on a single protocol.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_protocol_info Get Protocol Info ~122
Get the canonical description of an agent payment protocol including creator, maturity level, repo URL, and what layer it operates at (authorization, commerce, or settlement). Use when the user asks about a specific protocol ('what is AP2?', 'who created MPP?', 'is x402 production ready?', 'what layer does ACP operate at?'). Use compare_protocols instead when comparing multiple protocols against each other.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | Protocol identifier (e.g., 'ap2' for Google's authorization layer, 'x402' for Coinbase's settlement layer). |
No output schema declared.
No examples provided.
scan_opportunities Scan Agent Payments Ecosystem ~199
Scan GitHub, Hacker News, and npm for new repos, packages, and discussions in the agent payments ecosystem (AP2, ACP, x402, MPP, UCP). Returns AI-classified and scored opportunities with recommended actions. Use when the user asks about recent activity, new developments, or opportunities in agent payments ('what's new in agent payments?', 'any new x402 repos?', 'scan for opportunities'). Use get_protocol_info instead for static protocol details, or compare_protocols for side-by-side comparison. Costs $0.01 USDC. Accepts: x402 (USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (e.g., 7 for last week, 30 for last month). Default 7. |
| min_score | number | – | Minimum opportunity score out of 20 (e.g., 12 for high-quality only, 8 for broader results). Default 12. |
No output schema declared.
No examples provided.
What is the io.github.goodmeta/intelligence-mcp server?
io.github.goodmeta/intelligence-mcp is listed in the public MCP registry as io.github.goodmeta/intelligence-mcp. Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP. This page covers its hosted endpoint (https://intel.goodmeta.co/mcp).
Is the io.github.goodmeta/intelligence-mcp server safe to use?
io.github.goodmeta/intelligence-mcp scores 87 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 io.github.goodmeta/intelligence-mcp server expose?
io.github.goodmeta/intelligence-mcp exposes 3 tools: scan_opportunities, get_protocol_info, compare_protocols. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.
Does the io.github.goodmeta/intelligence-mcp server require authentication?
No. We connected to io.github.goodmeta/intelligence-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.goodmeta/intelligence-mcp server still maintained?
io.github.goodmeta/intelligence-mcp is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.