intelligence-mcp

Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP.

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
73%
Naming quality
87%
Poisoning risk
80%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • HIGHTool poisoning patterns detected
  • INFOTool description contains placeholder or incomplete textin scan_opportunities

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~644Tokens (tool definitions)
~767 BTypical response size
Moderate attention impact (0.50% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "intelligence-mcp": {
      "command": "npx",
      "args": [
        "@goodmeta/intelligence-mcp"
      ]
    }
  }
}

Runnable packages

npm@goodmeta/intelligence-mcp0.1.4stdio

Remote endpoints

https://intel.goodmeta.co/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢scan_opportunities(days, min_score)

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).

Input Schema

{
  "type": "object",
  "properties": {
    "days": {
      "default": 7,
      "description": "Look-back window in days (e.g., 7 for last week, 30 for last month). Default 7.",
      "type": "number"
    },
    "min_score": {
      "default": 12,
      "description": "Minimum opportunity score out of 20 (e.g., 12 for high-quality only, 8 for broader results). Default 12.",
      "type": "number"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_protocol_info(protocol)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "protocol": {
      "type": "string",
      "enum": [
        "ap2",
        "acp",
        "x402",
        "mpp",
        "ucp"
      ],
      "description": "Protocol identifier (e.g., 'ap2' for Google's authorization layer, 'x402' for Coinbase's settlement layer)."
    }
  },
  "required": [
    "protocol"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢compare_protocols

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

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools