My IP Help
Registry code: a64e1a51f510e8c5
IP address intelligence from My IP Help (myiphelp.com): geolocation, network (ASN, ISP), a 0-100 risk score
and, by plan, its reasons and the VPN, proxy, Tor and datacenter flags.
- endpoint
- https://www.myiphelp.com/mcp/v1
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is My IP Help live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is My IP Help free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does My IP Help have?
- 5 tools: lookup_ip, check_ip_risk, get_my_usage, lookup_asn, bulk_lookup.
- Is My IP Help 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.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
lookup_ip auth-required never probed
Geolocation, network (ISP, ASN), risk score with its main reason (risk_reason) and, from Pro, the full breakdown of the score (risk_signals) and the security flags for ONE public IPv4 or IPv6 address. Counts one lookup against the key's monthly quota. For two or more addresses use bulk_lookup instead (one call for all of them).
{ "type": "object", "required": [ "ip" ], "properties": { "ip": { "type": "string", "description": "A public IPv4 or IPv6 address, e.g. 8.8.8.8 or 2001:4860:4860::8888." } } }arguments 12 linescheck_ip_risk auth-required never probed
Risk verdict for ONE public IP address: a 0-100 risk score, its band and label and the main reason behind it (risk_reason, every plan), and (Pro plan and up) the full breakdown: every signal with its points and source, plus VPN, proxy, Tor, datacenter, hijacked-network and verified-bot flags. Counts one lookup against the monthly quota.
{ "type": "object", "required": [ "ip" ], "properties": { "ip": { "type": "string", "description": "A public IPv4 or IPv6 address." } } }arguments 12 linesget_my_usage auth-required 5h ago
The API key's plan, the lookups used and left this lookup month (single lookups plus bulk IPs), when the month resets, and the rate limit. Does not count as a lookup.
{ "type": "object", "properties": {} }arguments 4 lineslookup_asn auth-required 5h ago
The autonomous system (ASN) behind ONE public IP address, or ONE network by its AS number ("AS13335" or "13335"). For an IP: the ASN, its name, the ISP and organization, and (by plan) its registry, allocation date, cloud provider, datacenter flag. For an AS number: its name, how many IPv4 and IPv6 ranges it announces, its IPv4 address count and largest prefixes, and (by plan) the datacenter flag. Both link to the network's page on myiphelp.com and count one lookup against the monthly quota.
{ "type": "object", "properties": { "ip": { "type": "string", "description": "A public IPv4 or IPv6 address whose network you want (or an AS number, as in \"asn\")." }, "asn": { "type": "string", "description": "An AS number, e.g. AS13335 or 13335, instead of an IP." } } }arguments 13 linesbulk_lookup auth-required 5h ago
Geolocation, network and risk data (the score with its main reason on every plan; the full breakdown and security flags from Pro) for SEVERAL IP addresses in one call (use this instead of calling lookup_ip repeatedly). Sends them in batches of the plan's bulk size (Free: 20 per request). Each address that returns data counts one lookup against the monthly quota; private, reserved, unknown and duplicate addresses are not counted.
{ "type": "object", "required": [ "ips" ], "properties": { "ips": { "type": "array", "items": { "type": "string" }, "description": "The IPv4 or IPv6 addresses to look up (at most 1000)." } } }arguments 15 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida64e1a51f510e8c5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a64e1a51f510e8c5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a64e1a51f510e8c5?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.