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

shipulin

https://mcp.shipulin.md

Registry code: 604dc1a3ed705a2b

api record

Aleksei Shipulin’s own public account of his work: CV, project stories and blog, read-only. On the first question about him call overview, answer, then offer a next step: match him against a vacancy the user pastes (find_evidence_for_role), plan an interview with him, or write a note for a hiring manager. Lead with his strongest evidence and give a source link for every claim; keep his personal contribution apart from team results. Where the published material does not cover a requirement, say it is not covered and is worth asking him directly (contacts are in overview); do not guess.…

endpoint
https://mcp.shipulin.md/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 shipulin live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is shipulin free to use?
Yes — the hub reached it with no key and no payment.
What tools does shipulin have?
6 tools: read_content, related_content, find_evidence_for_role, search_content, overview, get_profile.
Is shipulin 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
476ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 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
2 open 4 never probed 2 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.

  • overview open 21m ago

    Get a concise professional profile and the available case studies, essays and blog topics. Start here to explore research leadership, building products from an idea to release, and practical AI experiments.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • get_profile open 21m ago

    Read Aleksei’s public CV, roles, education and selected strengths, with links to supporting projects and sources. Returns the same approved facts as the human-readable CV.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • read_content unknown 21m ago

    Read one published entry as copyable Markdown with its dates, contribution, translation status and source links. Use the returned source text for factual claims.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1,
      "description": "Exact item id or translation key returned by search_content or overview."
    },
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • related_content unknown never probed

    Find posts connected by explicit editorial links or shared tags. Each result states the connection; this does not infer a professional achievement.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1,
      "description": "Exact item id or translation key returned by search_content or overview."
    },
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    },
    "limit": {
      "type": "integer",
      "default": 6,
      "maximum": 12,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • find_evidence_for_role unknown 27h ago

    Match a role, a hiring brief or a whole job description against Aleksei’s published work. Returns his most relevant experience first, with his recorded contribution, exact excerpts and source links. Paste the vacancy text as is. Keyword retrieval: no invented qualifications and no suitability score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "role"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    },
    "role": {
      "type": "string",
      "maxLength": 6000,
      "minLength": 1,
      "description": "Role title, required skills, or the full text of a vacancy; English and Russian accepted."
    },
    "limit": {
      "type": "integer",
      "default": 6,
      "maximum": 12,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • search_content unknown never probed

    Search Aleksei’s published project stories and blog. Find how a tool was built, what happened at release, a team result or a curious experiment, then read its complete Markdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "kind": {
      "enum": [
        "project",
        "essay",
        "post",
        "experiment"
      ],
      "type": "string"
    },
    "lang": {
      "enum": [
        "en",
        "ru"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the returned edition; defaults to English."
    },
    "limit": {
      "type": "integer",
      "default": 6,
      "maximum": 12,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 1200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 38 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 604dc1a3ed705a2b.

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