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

protologue

https://mcp.protologue.com

Registry code: 903ab33a7919e943

api record

Protologue is an openly licensed (CC BY 4.0) reference taxonomy of prompting and large language model techniques. Use search_terms to find a technique, get_term for its sourced definition, and get_related to explore broader, narrower and related techniques. When you use a definition, cite it with the returned citation and link to its url.

endpoint
https://mcp.protologue.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 protologue live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is protologue free to use?
Yes — the hub reached it with no key and no payment.
What tools does protologue have?
4 tools: search_terms, get_related, list_categories, get_term.
Is protologue 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
62ms

last good check

priced tools
0

of 4 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 4 tools
3 open 1 never probed 3 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.

  • get_related open 2h ago

    List the techniques Protologue links to a given technique: broader (it is a kind of), narrower (kinds of it) and related.

    mcp-tool

    {
  "type": "object",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string",
      "description": "Technique name, synonym, slug or PTL identifier."
    }
  }
}
    arguments 12 lines
  • list_categories open 2h ago

    List Protologue's branches (categories) and the techniques in each.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_term open 2h ago

    Get the full Protologue entry for one technique: definition, description, synonyms, introduction year, primary sources, canonical URL, permanent identifier and a ready-made citation. Accepts a name, synonym, slug (e.g. 'react') or identifier (e.g. 'PTL-0058').

    mcp-tool

    {
  "type": "object",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string",
      "description": "Technique name, synonym, slug or PTL identifier."
    }
  }
}
    arguments 12 lines
  • search_terms unknown never probed

    Search Protologue for prompting and LLM techniques by name, synonym or keyword. Returns matching entries with their one-sentence definitions and canonical URLs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum number of results."
    },
    "query": {
      "type": "string",
      "description": "Technique name, synonym or keyword, e.g. 'chain of thought' or 'RAG'."
    }
  }
}
    arguments 19 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 903ab33a7919e943.

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

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.