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

WordPress Core Trac

https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev

Registry code: 8a6237e431d337c4

api record

Integrates with WordPress.org Trac instances across Core, Meta, Plugins, Themes, bbPress, BuddyPress, and GlotPress to search tickets, retrieve detailed information with comments, access changeset diffs, monitor timeline activity, and query metadata.

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

endpoint
https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev/mcp
protocol
streamable-http ·2024-11-05
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 WordPress Core Trac live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is WordPress Core Trac free to use?
Yes — the hub reached it with no key and no payment.
What tools does WordPress Core Trac have?
5 tools: getChangeset, getTracInfo, getTicket, getTimeline, searchTickets.
Is WordPress Core Trac 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
121ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 360 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
developer tools code & repositories
used for
  • search wordpress trac tickets
  • get ticket details with comments
  • get changeset diff
  • view recent trac timeline
takes → gives
text → data, code
tools
5 reads
_ 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 5 tools
4 open 1 never probed 4 of 5 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.

  • getTracInfo reads open 16h ago

    Get WordPress Core metadata like components, milestones, priorities, and severities.

    mcp-tool

    {
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "enum": [
        "components",
        "milestones",
        "priorities",
        "severities"
      ],
      "type": "string",
      "description": "Type of Trac information to retrieve"
    }
  }
}
    arguments 18 lines
  • getTicket reads open 16h ago

    Get detailed information about a specific WordPress Core ticket including description, comments, and metadata.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "number",
      "description": "Trac ticket ID number"
    },
    "commentLimit": {
      "type": "number",
      "default": 10,
      "description": "Maximum number of comments to return (default: 10, max: 50)"
    },
    "includeComments": {
      "type": "boolean",
      "default": true,
      "description": "Include ticket comments and discussion (default: true)"
    }
  }
}
    arguments 22 lines
  • getTimeline reads open 16h ago

    Get recent activity from WordPress Core timeline including recent tickets, commits, and other events.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "default": 7,
      "description": "Number of days to look back (default: 7, max: 30)"
    },
    "limit": {
      "type": "number",
      "default": 20,
      "description": "Maximum number of events to return (default: 20, max: 100)"
    }
  }
}
    arguments 15 lines
  • searchTickets reads open 9h ago

    Search for WordPress Core tickets by keyword or filter expression. Returns ticket summaries with basic info.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 10,
      "description": "Maximum number of results to return (default: 10, max: 50)"
    },
    "query": {
      "type": "string",
      "description": "Search query for tickets (keywords or filter expressions like 'summary~=keyword')"
    },
    "status": {
      "type": "string",
      "description": "Filter by ticket status (e.g., 'open', 'closed', 'new')"
    },
    "component": {
      "type": "string",
      "description": "Filter by component name (e.g., 'Administration', 'Posts, Post Types')"
    }
  }
}
    arguments 25 lines
  • getChangeset reads unknown never probed

    Get information about a specific WordPress Core changeset/commit including commit message, author, and diff.

    mcp-tool

    {
  "type": "object",
  "required": [
    "revision"
  ],
  "properties": {
    "revision": {
      "type": "number",
      "description": "SVN revision number (e.g., 58504)"
    },
    "diffLimit": {
      "type": "number",
      "default": 2000,
      "description": "Maximum characters of diff to return (default: 2000, max: 10000)"
    },
    "includeDiff": {
      "type": "boolean",
      "default": true,
      "description": "Include diff content (default: true)"
    }
  }
}
    arguments 22 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 8a6237e431d337c4.

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