mcp-registry/com.pixserp/search · v1.0.0
As of 2026-10-23 12:57 UTC, the Pixserp Search MCP server is unknown with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Point your MCP client at this streamable-http endpoint: https://pixserp.com/api/v1/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,618 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.pixserp%2Fsearch/fixes
{
"name": "search",
"description": "Search the live web and get an AI-synthesized answer with structured citations. One endpoint covers 10 answer shapes — web, news, images, places & maps, shopping, flights, hotels, YouTube, transcripts, any URL — the right one is picked automatically from your query. Use this whenever you need fresh, factual information from the web.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"model": {
"enum": [
"pixserp-fast",
"pixserp-standard",
"pixserp-deep",
"pixserp-agent"
],
"type": "string",
"default": "pixserp-fast",
"description": "`pixserp-fast` = quick single-search lookup (default). `pixserp-standard` = balanced. `pixserp-deep` = multi-angle thorough research. `pixserp-agent` = multi-step research loop, decides itself when to stop."
},
"query": {
"type": "string",
"description": "What to search for. Phrase as a natural-language question or a specific topic."
},
"max_steps": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Only used when `model = pixserp-agent`. Caps the research loop length. Default 50, max 100."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}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.pixserp/search"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.pixserp/search"}) over MCP.
search ~306 tokensStatic 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.pixserp%2Fsearch?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.pixserp%2Fsearch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pixserp%2Fsearch.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pixserp%2Fsearch.svg :target: https://glimind.com/server/mcp-registry%2Fcom.pixserp%2Fsearch?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:055fb0cf5bbd2f19…, first seen 2026-10-17, included at leaf 14812 of 56,523. Version history · verify what your client received.
Compare: most reliable search servers
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.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 12:57 UTC, the Pixserp Search MCP server is unknown with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Pixserp Search MCP server advertises 1 tool, including search.
Point your MCP client at this streamable-http endpoint: https://pixserp.com/api/v1/mcp
Glimind scanned all 1 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.
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.