_ registry / mcp streamable-http · checked 2h ago

AgentSec MCP

https://agentsec-mcp.agentsec-mcp.workers.dev

Registry code: 2a0f703231ef671e

api record

Security intelligence via x402 on Base. CVE lookup, IP reputation, secret scanning.

from a public catalogue that lists it, not from the operator

endpoint
https://agentsec-mcp.agentsec-mcp.workers.dev/mcp
protocol
streamable-http ·2025-11-25
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is AgentSec MCP live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is AgentSec MCP free to use?
No — it charges per call, from 0.01 USDC, quoted in its own 402 answers.
What tools does AgentSec MCP have?
3 tools: secret_scan, reputation_check, cve_lookup.
Is AgentSec MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
297ms

last good check

priced tools
1

of 3 tools

_ answered our checks, 90 days 406 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
security & compliance threat & vulnerability
used for
  • look up cves for a package
  • check ip or domain reputation
  • scan text for secrets
takes → gives
text, code → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 paid 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cve_lookup reads 0.01 USDC paid 2h ago

    Look up known CVE vulnerabilities for an npm package+version or a specific CVE ID. Returns CVSS scores, descriptions, and fix versions from NVD and OSV. Results are cached for 10 minutes. Costs $0.01 USDC per call.

    mcp-tool

    {
  "type": "object"
}
    arguments 3 lines
  • secret_scan reads unknown never probed

    Scan text content for hardcoded secrets, API keys, and credentials using 20 pre-compiled patterns. Privacy guarantee: Input text is NEVER logged, cached, stored, or forwarded. Only findings_count and finding offsets (not matched values) are returned. Detected pattern types include: AWS keys, GitHub/GitLab PATs, OpenAI/Anthropic keys, Stripe secrets, Slack tokens, PEM private keys, JWT tokens, and 13 more. Per-call rate limit: 100/min. Payment: $0.05 USDC per scan.

    mcp-tool

    {
  "type": "object"
}
    arguments 3 lines
  • reputation_check reads unknown never probed

    Check the reputation of an IP address or domain using AbuseIPDB and VirusTotal. Returns a security verdict (malicious/suspicious/unknown/clean) with confidence signals. Verdict is conservative: incomplete data returns 'unknown' never 'clean'. Results are cached for 10 minutes. Costs $0.01 USDC per call.

    mcp-tool

    {
  "type": "object"
}
    arguments 3 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2a0f703231ef671e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a0f703231ef671e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2a0f703231ef671e/badge.svg)](https://brick.blue/agent/2a0f703231ef671e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.