mcpbeat Sign in

Parc Dev Task Breakdown Server MCP Server

not responding

Parc Dev Task Breakdown Server is listed as active in the registry but did not answer our last check.

Break down complex problems into clear, actionable steps. Adapt on the fly by iterating, revising,…

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
606 ms
Response time
average over 24h
open, no key
Access
streamable-http

Parc Dev Task Breakdown Server does not always answer

Over the last week it answered 0.0% 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 4 min ago.

run in your terminal
claude mcp add Parc-Dev-task-breakdown-server --transport http https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp
Settings → Connectors → Add custom connector, then paste this address
https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp
~/.codex/config.toml
[mcp_servers.Parc-Dev-task-breakdown-server]
url = "https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "Parc-Dev-task-breakdown-server": {
      "url": "https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "Parc-Dev-task-breakdown-server": {
      "type": "http",
      "url": "https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://server.smithery.ai/@Parc-Dev/task-breakdown-server/mcp streamable-http answering 606 ms 4 min ago

Alternatives to Parc Dev Task Breakdown Server

same job, measured the same way
SuggestionBox.tips
by suggestionbox

Leave a private suggestion, problem or compliment for any business. Only the business reads it.

2 tools answering
SkoIA Parts
by macacoengenhocas

Resolve part problems, check compatibility and identify only the information still missing.

15 tools answering
Brent Burgess
by brentburgess

Read-only facts from brentburgess.com: profile, writing, projects and the site's own datasets.

7 tools answering
Renpy Release Gate
by jmshinhwa

Find the .rpy lines that compile clean and only break inside a player's save

61 installs/wk local only
Gildara
by gildara

Operating contracts for AI agents. Structured instructions compiled into system prompts.

local only
AgentRead
by workers-toolschemaforge-agent-read

Turn URLs, PDFs and DOCX into clean Markdown for agents, plus prompt-injection scanning

2 tools answering
Sequentum
by sequentum

Turn the web into structured, reliable, actionable enterprise data for AI Agents

answering
Systemia Field Library
by jgaethle10

Match contractor operating problems to practical Field Library playbooks. Read-only discovery.

3 tools answering

Parc Dev Task Breakdown Server — questions

Answers built from our own checks of this server.

Is Parc Dev Task Breakdown Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 606 ms. The bar chart above shows every period we have measured.
The registry lists Parc Dev Task Breakdown Server as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Parc Dev Task Breakdown Server?
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 Parc Dev Task Breakdown Server need an API key?
No. Parc Dev Task Breakdown Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.