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

skillspicker

https://skillspicker.com

Registry code: 3b215e1d5e312c19

api record

Use recommend_skills when the user starts or sets up a project, asks which agent skills, Claude Code skills, Cursor rules or SKILL.md files to install, or wants their coding agent tuned for a stack. Find open-license agent skills (SKILL.md) for a project. Prefer passing tags you derived from the local project files (languages, frameworks, services, tasks) so no code leaves the machine. The tool returns how many skills match, two free picks with install commands, and a link to the full curated list.

endpoint
https://skillspicker.com/mcp
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 it live, free and safe measured by this hub
Is skillspicker live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is skillspicker free to use?
Not measured yet.
What tools does skillspicker have?
1 tool: recommend_skills.
Is skillspicker 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
203ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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

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

  • recommend_skills unknown 1h ago

    Recommend free, open-license agent skills (SKILL.md) for the current project. Call this when the user starts a new project or sets up a repo, asks which skills or plugins to add to Claude Code, Cursor, Codex, Copilot or Gemini CLI, mentions SKILL.md, Cursor rules or agent skills, or asks how to make the coding agent better at their stack (for example Next.js, FastAPI, Django, Expo, Supabase, Stripe, Cloudflare Workers, Rust, Go). Prefer tags you derive from local files (package.json, pyproject.toml, go.mod, Cargo.toml) so no code leaves the machine; a short description or a public GitHub repo URL also works. Read-only. Returns how many of 3,000+ indexed skills match, 2 picks with source, license and install command, and a link to the full ranked list ($9 one time).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Stack and task tags, for example [\"typescript\",\"nextjs\",\"tailwind\",\"supabase\",\"testing\"]. Full list: https://skillspicker.com/rules.json"
    },
    "repo_url": {
      "type": "string",
      "description": "Public GitHub repo URL. We read the file list and manifest files, nothing else."
    },
    "description": {
      "type": "string",
      "description": "One or two sentences about the project, if you have no tags."
    }
  }
}
    arguments 20 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 3b215e1d5e312c19.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3b215e1d5e312c19/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/3b215e1d5e312c19/badge.svg)](https://brick.blue/agent/3b215e1d5e312c19?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
50%

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.