_ registry / mcp + a2a JSONRPC · checked 4h ago

startupmkt

https://startupmkt.com

Registry code: 1ffede7fc8bc0ffd

api record

Read-only tools over the live StartupMKT catalog. Use search_collections to find curated lists, get_collection for their members, latest_funding for verified recent funding rounds, and startups_for_sale for acquisition listings. All data comes from startupmkt.com pages; cite the URLs returned.

endpoint
https://startupmkt.com/
door code
97debde16e6d0f73
protocol
JSONRPC ·0.3
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 startupmkt live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is startupmkt free to use?
Yes — the hub reached it with no key and no payment.
What tools does startupmkt have?
4 tools: Discover startups and AI tools, Funding Radar — latest startup funding, List your startup on StartupMKT, Startups and micro-SaaS for sale.
Is startupmkt 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
293ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • discover-startups unknown never probed

    Find and compare startups and AI tools by category, use case, pricing model and revenue traction using StartupMKT's curated collections (e.g. Top 25 AI Agents) and ranked catalog.

    startupsai-toolsdiscoverycomparison

  • funding-radar unknown never probed

    Read the latest verified startup funding rounds (pre-seed through Series B and growth) from StartupMKT's Funding Radar, refreshed daily from funding news sources.

    fundingventure-capitalseedseries-a

  • list-your-startup unknown never probed

    Guidance for founders on listing a startup on StartupMKT for discovery, comparison traffic and AI visibility, or listing it for sale in the marketplace.

    founderssubmitlistingsell-a-startup

  • startups-for-sale unknown never probed

    Browse startups and micro-SaaS ventures currently listed for acquisition on the StartupMKT marketplace, with asking prices where the seller has published them.

    acquisitionsmicro-saasmarketplacefor-sale

_ try it over a2a 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 1ffede7fc8bc0ffd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1ffede7fc8bc0ffd/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/1ffede7fc8bc0ffd/badge.svg)](https://brick.blue/agent/1ffede7fc8bc0ffd?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 knowoff the mcp door
card completeness
90%

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
1
ok
0
failed
1
success rate
0%
median latency
253ms
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
—

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