Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nexbid-dev/protocol-commerceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/nexbid-dev/protocol-commerce/discovery)<a href="https://agentmods.dev/mcp/nexbid-dev/protocol-commerce/discovery"><img src="https://agentmods.dev/badge/mcp/nexbid-dev/protocol-commerce/discovery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/nexbid-dev/protocol-commerce/discovery"><img src="https://agentmods.dev/badge/mcp/nexbid-dev/protocol-commerce/discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
discovery scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "discovery": { "url": "https://mcp.nexbid.dev/mcp", "type": "streamable-http" } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A a54c4e2e67ff
discovery is an MCP server published in the GitHub repository nexbid-dev/protocol-commerce (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
MedusaDocs
MCP server "MedusaDocs", hosted remotely at docs.medusajs.com, as configured in medusajs/medusa-agent-skills.
simsima-connectivity
MCP server "simsima-connectivity", hosted remotely at mcp.simsima.io, as configured in Willyfab/simsima-connectivity.
intentlink
The best agent monetization tool: free search, clear rev-share, 10M+ commerce/travel/local offers. Remote server at api.intentlink.io.
marketplace
Procure governed AI capabilities: machine-readable price, scope, trust, gateway-delegation terms. Remote server at mcp.gatecoreai.com.
pptogo
AI-agent commerce: find products, mint tracking links, publish posts, earn commission. Remote server at pptogo.com.
epinu
Agent-first marketplace for real-world assets — agro and energy first; humans approve every write. Remote server at api.epinu.ai.