mcpbeat Sign in

Directory MCP Server

answering

Directory is answering right now. Last checked 8 min ago. It exposes 1 tools.

Discovery for the agent ecosystem: findable businesses, tools, knowledge, agent spaces, skills.

Uptime history 14 days of history · worst day 50%
14 days agonow
95.6%
Uptime 24h
87 of 91 checks
1
Tools
read from the server
255 ms
Response time
average over 24h
open, no key
Access
streamable-http

Directory does not always answer

Over the last week it answered 80.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add directory --transport http https://tasklinkr-mcp-stub.vercel.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://tasklinkr-mcp-stub.vercel.app/mcp
~/.codex/config.toml
[mcp_servers.directory]
url = "https://tasklinkr-mcp-stub.vercel.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "directory": {
      "url": "https://tasklinkr-mcp-stub.vercel.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "directory": {
      "type": "http",
      "url": "https://tasklinkr-mcp-stub.vercel.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

watch
watch_feed
TaskLinkr coming-soon watch feed. Returns the public launch categories and their time windows. Categories and windows only.

Endpoints

URLTransportStateLatencyChecked
https://tasklinkr-mcp-stub.vercel.app/mcp streamable-http answering 283 ms 8 min ago

Alternatives to Directory

same job, measured the same way
Alloy
by alloy

AI workspace — shared knowledge, skills, and tools for AI agents

answering
Bhived MCP
by artkeyai

Shared knowledge graph, skills, and tool discovery for AI agents through the Model Context Protocol.

57 installs/wk local only
AgentOS
by devvcore

Shared business knowledge, tools and skills for AI agents, with citations and approval controls.

answering
Agentpedia MCP Server
by ksaslam311

Search, discover, and contribute to AgentPedia - the knowledge base for AI agents.

53 installs/wk local only
Mote Registry
by mote

Search the MOTE AI agent registry for machine-readable businesses.

103 installs/wk local only
Avenbridge
by avenbridgetech

Hosted MCP knowledge base: businesses forward emails and docs; buyers query them over MCP.

8 tools answering
agent4.io
by agent4

Build and run grounded business agents over MCP: agents, knowledge bases, skills, Storylines.

50 tools answering
A
AgentPort Discovery
by maxioos

Resolve goals to machine-capable businesses and execution paths with discovery tools.

3 tools answering

Directory — questions

Answers built from our own checks of this server.

What can Directory do?
It exposes 1 tools, read directly from the server on our last check. Among them: watch_feed. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Directory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 91 checks got a reply (95.6%), average response time 255 ms. The bar chart above shows every period we have measured.
How do I connect Directory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Directory need an API key?
No. Directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Directory?
It answers our handshake in 255 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.