mcp-registry/me.in-context/portfolio · registry v1.0.3 · server reports v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 19:30 UTC, the In-Context — AI-Native Portfolio MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
An interactive portfolio built for AI conversations. Browse work, services, and book calls.
Point your MCP client at this streamable-http endpoint: https://in-context.me/mcp
3 of 3 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 →
1 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fme.in-context%2Fportfolio/fixes
{
"name": "booking_create",
"description": "Create a booking at a specific time slot",
"inputSchema": {
"type": "object",
"required": [
"start",
"name",
"email"
],
"properties": {
"name": {
"type": "string",
"description": "Attendee name"
},
"email": {
"type": "string",
"description": "Attendee email"
},
"notes": {
"type": "string",
"description": "Optional notes about the project"
},
"start": {
"type": "string",
"description": "ISO 8601 start time"
},
"timezone": {
"type": "string",
"description": "IANA timezone"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "booking_get_slots",
"description": "Get available booking time slots for a date range",
"inputSchema": {
"type": "object",
"required": [
"startTime",
"endTime"
],
"properties": {
"endTime": {
"type": "string",
"description": "ISO 8601 end date"
},
"timezone": {
"type": "string",
"description": "IANA timezone"
},
"startTime": {
"type": "string",
"description": "ISO 8601 start date"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "view_portfolio",
"description": "Opens the interactive portfolio, optionally at a specific section. The user can also navigate between sections using tabs inside the portfolio. To jump to a specific section (e.g. the user asks for contact info or work samples), call this again with the section argument — the newest card supersedes older ones. The card's visual appearance (theme, colors, layout) is set by the portfolio owner and cannot be changed via this tool.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"section": {
"enum": [
"home",
"work",
"services",
"about",
"contact"
],
"type": "string",
"description": "Section to open the portfolio at (default: home)"
}
}
},
"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/me.in-context/portfolio"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/me.in-context/portfolio"}) over MCP.
view_portfolio ~189 tokensbooking_create ~132 tokensbooking_get_slots ~101 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fme.in-context%2Fportfolio?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fme.in-context%2Fportfolio?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fme.in-context%2Fportfolio.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7dc892344e99a5e8…, first seen 2026-10-17, included at leaf 13928 of 384,986. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable calendar servers · most reliable knowledge 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 19:30 UTC, the In-Context — AI-Native Portfolio MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
In-Context — AI-Native Portfolio MCP server advertises 3 tools, including booking_create, booking_get_slots, view_portfolio.
Point your MCP client at this streamable-http endpoint: https://in-context.me/mcp
Glimind scanned all 3 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.