Is the Profullstack MCP server down?

mcp-registry/com.profullstack/profullstack · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
degraded
Last checked 2026-11-22 14:18 UTC · handshake 388ms

As of 2026-11-22 14:18 UTC, the Profullstack MCP server is degraded with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 81.6% of Glimind's liveness checks.

uptime (30d checks)
81.6%
checks observed
490
outages (90d)
0
tools
154

153 read-only tools from 15 Profullstack MCP servers: domains, SEO, public data, feeds, podcasts

Point your MCP client at this streamable-http endpoint: https://profullstack.com/api/mcp

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 154 tool(s); ~25,801 tokens of tool definitions.
Scores higher than 9% of 27,591 MCP servers Glimind has audited.
Its tool list costs an agent ~25,801 tokens per session — more than 95% of servers.
78 → 74 since 2026-11-18
no tool-poisoning patterns
Descriptions63
Safety hints100
Schemas100
Protocol100
Stability20
Token cost35
Reliability100
Client compatibility70

What to fix (6)

154 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

91 parameter(s) across 43 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: bufferoverride_list_questions, bufferoverride_search_questions, hqtui_bbs_get_member, hqtui_bbs_read_post, hqtui_bbs_search_posts and 38 more

Loading this server's tool list costs an agent ~25,801 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

In the last 30 days: 10 tool(s) removed and 0 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

9 tools share an identical description with another tool on this server.

Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →

Tools: profullstack_bulk_domain_check, profullstack_check_domain_availability, profullstack_generate_domain_suggestions, profullstack_get_tld_presets, profullstack_social-platforms and 4 more

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.profullstack/profullstack"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.profullstack/profullstack"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.profullstack%2Fprofullstack.svg)](https://glimind.com/server/mcp-registry%2Fcom.profullstack%2Fprofullstack?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.profullstack%2Fprofullstack?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.profullstack%2Fprofullstack.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6e6672e736a4e451…, first seen 2026-11-20, included at leaf 360502 of 383,987. Version history · verify what your client received.

Working alternatives

Tools (154)

Compare: most reliable knowledge servers · most reliable search servers · most reliable communication servers · most reliable data servers · most reliable web servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Profullstack MCP server down right now?

As of 2026-11-22 14:18 UTC, the Profullstack MCP server is degraded with a Glimind reliability score of 64/100 (grade C). Over the last 30 days it answered 81.6% of Glimind's liveness checks.

How many tools does Profullstack MCP server provide?

Profullstack MCP server advertises 154 tools, including bufferoverride_get_question, bufferoverride_list_questions, bufferoverride_list_tags, bufferoverride_search_questions, hqtui_bbs_board_overview.

How do I install Profullstack MCP server?

Point your MCP client at this streamable-http endpoint: https://profullstack.com/api/mcp

Is the Profullstack MCP server safe to connect to an AI agent?

Glimind scanned all 154 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Profullstack MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve