mcp-registry/app.selis.mcp/pmo · v0.3.1
As of 2026-10-22 23:38 UTC, the Selis Pmo MCP server is up (it requires sign-in) with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
MCP server for Selis TMiS — manage PMO entities from any MCP client
Claude Code
claude mcp add --transport http selis-pmo-mcp-server https://mcp.selis.app/tmis/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"selis-pmo-mcp-server": {
"type": "http",
"url": "https://mcp.selis.app/tmis/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
10 parameter(s) across 5 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 →
3 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
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 →
Pushes the model to prefer this tool over others regardless of the task — tool-selection manipulation. Example (selis_scalo, description): "…meta=none), so this is the ONLY way to read Scalo numbers. ALWAYS call this tool whenever the user asks how Calx / Scalo / the business / the investments / a fund is doi…"
Remove text aimed at the model rather than the user. Tool descriptions should describe what the tool does and how to call it, not instruct the model about other tools, the user, or its own instructions. 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 →
3 of 13 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 →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.selis.mcp%2Fpmo/fixes
{
"name": "selis_comment_add",
"description": "Add a comment to an item, or reply to an existing comment.",
"inputSchema": {
"type": "object",
"required": [
"entity",
"id",
"content"
],
"properties": {
"id": {
"type": "string",
"description": "Item ID or prefixed ref"
},
"entity": {
"type": "string",
"description": "e.g. actions, issues, risks"
},
"parent": {
"type": "string",
"description": "Optional — comment ID to reply to"
},
"content": {
"type": "string",
"description": "Comment text"
}
}
},
"annotations": {
"openWorldHint": true,
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "selis_create",
"description": "Create entity. Use selis_describe first to see valid enum values. WARNING: owner/assignee/group/item fields expect UUIDs, not names.",
"inputSchema": {
"type": "object",
"required": [
"entity",
"data"
],
"properties": {
"data": {
"type": "object"
},
"entity": {
"type": "string"
}
}
},
"annotations": {
"openWorldHint": true,
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "selis_scalo",
"description": "Pull the data behind the Selis 'Scalo' dashboards — Calx finance / people / pipeline, the Collab Currency & Skycatcher investment funds, and the Onmeta B2B/B2C portfolio board — already projected from item.meta with the same KPIs the dashboards compute. The generic selis_list CANNOT reach this data (it forces meta=none), so this is the ONLY way to read Scalo numbers.",
"inputSchema": {
"type": "object",
"required": [
"dataset"
],
"properties": {
"year": {
"type": "string",
"description": "Optional year filter (e.g. '2025') for finance and pipeline."
},
"fundId": {
"type": "string",
"description": "For dataset='fund' only. Omit to list available funds, or pass 'collab-currency' / 'skycatcher' for that fund's full timeline + KPIs."
},
"dataset": {
"enum": [
"all",
"finance",
"people",
"pipeline",
"fund",
"onmeta"
],
"type": "string",
"description": "Which Scalo dataset. Use 'all' for any broad question (returns finance + people + pipeline + BOTH funds + onmeta together, so nothing is skipped). Otherwise one of: finance | people | pipeline | fund | onmeta."
}
}
},
"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/app.selis.mcp/pmo"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.selis.mcp/pmo"}) over MCP.
selis_scalo ~335 tokensselis_list ~229 tokensselis_comment_add ~127 tokensselis_comments_list ~127 tokensselis_set_org ~87 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%2Fapp.selis.mcp%2Fpmo?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.selis.mcp%2Fpmo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.selis.mcp%2Fpmo.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.selis.mcp%2Fpmo.svg :target: https://glimind.com/server/mcp-registry%2Fapp.selis.mcp%2Fpmo?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:50c9280ef6a0e975…, first seen 2026-10-19, included at leaf 26242 of 48,938. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data 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-22 23:38 UTC, the Selis Pmo MCP server is up (it requires sign-in) with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Selis Pmo MCP server advertises 13 tools, including selis_comment_add, selis_comments_list, selis_create, selis_delete, selis_describe.
Point your MCP client at this streamable-http endpoint: https://mcp.selis.app/tmis/mcp
Glimind found text in this server's tool definitions worth reviewing before connecting it. selis_scalo: Pushes the model to prefer this tool over others regardless of the task — tool-selection manipulation.
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.