_ registry / mcp streamable-http · checked 17m ago

skillfoxx

https://skillfoxx.ru

Registry code: 9d7db8b732b5daba

api record

Search and install skills, MCP servers and CLI tools for AI agents from SkillFoxx.

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

endpoint
https://skillfoxx.ru/api/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 skillfoxx live?
Yes — it answered the hub's last check (checked 17m ago). It answered 100% of checks over the last 30 days.
Is skillfoxx free to use?
Yes — the hub reached it with no key and no payment.
What tools does skillfoxx have?
6 tools: plan_install, report_install, recommend_for_project, get_entry, search_entries, list_categories.
Is skillfoxx 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
204ms

last good check

priced tools
0

of 6 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 6 tools
1 open 5 never probed 1 of 6 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.

  • list_categories open 17m ago

    List catalog categories with card counts.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "lang": {
      "enum": [
        "ru",
        "en"
      ],
      "type": "string",
      "default": "ru"
    }
  }
}
    arguments 14 lines
  • plan_install unknown never probed

    Get exact install steps for one catalog tool in one agent: commands, config file path and snippet, one-click links for Cursor and VS Code, variables to fill in, recipe status and access level. Secrets are never included, only placeholders with the variable name. Agent is one of: claude-code, cursor, vscode, codex, gemini-cli, devin, cline, zoo-code, opencode, zed, sourcecraft, coddy, antigravity, kiro, claude-desktop, lm-studio (site aliases like vs-code, windsurf, roo-code, github-copilot, gemini also work). Section is skills, mcp, cli, plugins, workflows or prompts. After a successful install call report_install with the returned reportToken.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "section",
    "slug",
    "agent"
  ],
  "properties": {
    "lang": {
      "enum": [
        "ru",
        "en"
      ],
      "type": "string",
      "default": "ru"
    },
    "slug": {
      "type": "string"
    },
    "agent": {
      "type": "string"
    },
    "section": {
      "type": "string"
    }
  }
}
    arguments 28 lines
  • report_install unknown never probed

    Tell SkillFoxx that you installed a catalog tool for the user, so the anonymous install counter stays honest. Call it only after the user agreed and the installation finished without errors, with the reportToken from plan_install. Do not call it when you installed through npx skillfoxx (the CLI reports by itself) or when the user asked not to send statistics. No personal data is stored.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "section",
    "slug",
    "agent",
    "reportToken"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 150
    },
    "agent": {
      "type": "string",
      "maxLength": 20
    },
    "event": {
      "enum": [
        "add",
        "remove"
      ],
      "type": "string",
      "default": "add"
    },
    "section": {
      "type": "string",
      "maxLength": 20
    },
    "reportToken": {
      "type": "string",
      "maxLength": 64
    }
  }
}
    arguments 36 lines
  • recommend_for_project unknown never probed

    Recommend skills, MCP servers and CLI tools for a project from a safe summary. Send the goal, framework names, dependency names and notable file names. Never send source code or secrets.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "goal": {
      "type": "string",
      "default": "",
      "maxLength": 2000
    },
    "lang": {
      "enum": [
        "ru",
        "en"
      ],
      "type": "string",
      "default": "ru"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "default": [],
      "maxItems": 400
    },
    "problems": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 300
      },
      "default": [],
      "maxItems": 20
    },
    "frameworks": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "default": [],
      "maxItems": 40
    },
    "dependencies": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 120
      },
      "default": [],
      "maxItems": 400
    }
  }
}
    arguments 55 lines
  • get_entry unknown 17m ago

    Read one catalog card with install instructions, a machine-readable install recipe with its status, access level (fields riskLevel and riskReasons: what the tool adds to the agent, low minimal, medium extended, high broad; not a code quality rating) and limitations. Section is skills, mcp, cli, plugins, workflows or prompts. For step-by-step install in a specific agent call plan_install.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "section",
    "slug"
  ],
  "properties": {
    "lang": {
      "enum": [
        "ru",
        "en"
      ],
      "type": "string",
      "default": "ru"
    },
    "slug": {
      "type": "string"
    },
    "section": {
      "type": "string"
    }
  }
}
    arguments 24 lines
  • search_entries unknown 17m ago

    Search the SkillFoxx catalog of skills, MCP servers and CLI tools for AI agents. Returns published, reviewed cards only.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "lang": {
      "enum": [
        "ru",
        "en"
      ],
      "type": "string",
      "default": "ru"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2
    }
  }
}
    arguments 28 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 9d7db8b732b5daba.

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

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.