mcp-registry/com.pinappai/mcp · v0.1.0
As of 2026-10-23 10:09 UTC, the Pinappai MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Visual website feedback your coding agent applies: pin change requests on the live site over MCP.
Claude Code
claude mcp add --transport http pinappai-mcp-server https://mcp.pinappai.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"pinappai-mcp-server": {
"type": "http",
"url": "https://mcp.pinappai.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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 →
4 of 38 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 →
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.pinappai%2Fmcp/fixes
{
"name": "update_me_profile",
"description": "Update the API key user's display name. Email is identity and not editable.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "The new display name."
}
},
"additionalProperties": false
},
"annotations": {
"idempotentHint": true,
"readOnlyHint": false,
"destructiveHint": false
}
}{
"name": "update_project",
"description": "Update editable fields on a project — slug, name, owner_email, allowed_origins, allow_anonymous_reviewers, primary_origin (review link), preview_origin (preview review link). Requires editor role.",
"inputSchema": {
"type": "object",
"required": [
"project"
],
"properties": {
"name": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "New display name for the project."
},
"slug": {
"type": "string",
"pattern": "^[a-z0-9][a-z0-9-]*$",
"maxLength": 64,
"minLength": 2,
"description": "New slug (renames the project; widget snippets keep working since they reference api_key, not slug)."
},
"project": {
"type": "string",
"minLength": 1,
"description": "Current project slug (the lookup key)."
},
"owner_email": {
"type": "string",
"format": "email",
"pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 254,
"description": "Reassign project ownership to a different email (for display only — does not change permissions)."
},
"preview_origin": {
"anyOf": [
{
"type": "string",
"format": "uri",
"maxLength": 255
},
{
"type": "null"
}
],
"description": "Optional branch/preview deploy origin. review.pinappai.com/p/<slug>~preview/ serves it so reviewers can check APPLIED changes before they ship — records still write against primary_origin. Set this after publishing an apply round to a preview deploy; null (or an empty string) clears it."
},
"primary_origin": {
"anyOf": [
{
"type": "string",
"format": "uri",
"maxLength": 255
},
{
"type": "null"
}
],
"description": "Canonical site origin powering the no-install review link (review.pinappai.com/p/<slug>/). Any URL is normalized down to its origin. null (or an empty string) clears it and disables the link."
},
"allowed_origins": {
"type": "array",
"items": {
"type": "string",
"maxLength": 255,
"minLength": 1
},
"maxItems": 20,
"description": "REPLACES the existing list. Pass an empty array [] to clear all allowed origins."
},
"allow_anonymous_reviewers": {
"type": "boolean",
"description": "When true, any verified email on a CORS-allowed origin can submit feedback. When false, the email must be on the workspace or project_reviewers list."
}
},
"additionalProperties": false
},
"annotations": {
"idempotentHint": true,
"readOnlyHint": false,
"destructiveHint": false
}
}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.pinappai/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.pinappai/mcp"}) over MCP.
pinappai_register_change_items ~615 tokensupdate_project ~599 tokensanalyze_patterns ~583 tokenspinappai_apply_change_requests ~484 tokenslist_change_requests ~438 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.pinappai%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.pinappai%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pinappai%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.pinappai%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.pinappai%2Fmcp?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:953e0c9582bcc33b…, first seen 2026-10-17, included at leaf 10395 of 51,453. Version history · verify what your client received.
Compare: most reliable data servers · most reliable productivity servers · most reliable security servers · most reliable other servers · most reliable retrieval 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 10:09 UTC, the Pinappai MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Pinappai MCP server advertises 38 tools, including analyze_patterns, archive_project, create_project, create_workspace, delete_workspace.
Point your MCP client at this streamable-http endpoint: https://mcp.pinappai.com/mcp
Glimind scanned all 38 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.