Selis MCP
REMOTE · MCP.SELIS.APP · 5 COMPONENTS · SCANNED SEP 28
MCP server for Selis TMiS — manage PMO entities from any MCP client
Recent critical change
Authorization (13 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Selis MCP server?
Selis MCP is a hosted endpoint at https://mcp.selis.app/tmis/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.selis.app
claude mcp add --transport http app-selis-mcp-pmo 'https://mcp.selis.app/tmis/mcp'
{
"mcpServers": {
"app-selis-mcp-pmo": {
"url": "https://mcp.selis.app/tmis/mcp"
}
}
} {
"servers": {
"app-selis-mcp-pmo": {
"type": "http",
"url": "https://mcp.selis.app/tmis/mcp"
}
}
} [mcp_servers.app-selis-mcp-pmo] url = "https://mcp.selis.app/tmis/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-selis-mcp-pmo": {
"type": "remote",
"url": "https://mcp.selis.app/tmis/mcp",
"enabled": true
}
}
} openclaw mcp add app-selis-mcp-pmo --url 'https://mcp.selis.app/tmis/mcp' --transport streamable-http
mcp_servers:
app-selis-mcp-pmo:
url: "https://mcp.selis.app/tmis/mcp" {
"McpServers": {
"app-selis-mcp-pmo": {
"Transport": "http",
"Url": "https://mcp.selis.app/tmis/mcp"
}
}
} assistant mcp add app-selis-mcp-pmo -t streamable-http -u 'https://mcp.selis.app/tmis/mcp'
{
"mcpServers": {
"app-selis-mcp-pmo": {
"type": "http",
"url": "https://mcp.selis.app/tmis/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 −24
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- Tool coverage: 92 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 13 Sept 26 +24
- Authorization: pass → fail ▼ critical
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 92 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 64 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: good functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.selis.app/tmis/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.selis.app | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 5e67950c59be42d5d670c190d8ba51d5725 |
| SANs: mcp.selis.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.selis.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| selis.app. | present | 30363 | 13 | Verified |
| mcp.selis.app. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.selis.app/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.selis.app/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.selis.app/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.selis.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.selis.app |
| Authorisation server | https://mcp.selis.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.selis.app/tmis/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.selis.app/tmis/mcp | HTTPS enforced | 301 | https://mcp.selis.app/tmis/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
selis_comment_add ~75
Add a comment to an item, or reply to an existing comment.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Comment text |
| entity | string | yes | e.g. actions, issues, risks |
| id | string | yes | Item ID or prefixed ref |
| parent | string | – | Optional — comment ID to reply to |
No output schema declared.
No examples provided.
selis_comments_list ~81
List comments for an item. If commentId is provided, returns that comment and its replies.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | – | Optional — get this specific comment + replies |
| entity | string | yes | e.g. actions, issues, risks |
| id | string | yes | Item ID or prefixed ref (e.g. ACT-0859) |
No output schema declared.
No examples provided.
selis_create ~54
Create entity. Use selis_describe first to see valid enum values. WARNING: owner/assignee/group/item fields expect UUIDs, not names.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| entity | string | yes | – |
No output schema declared.
No examples provided.
selis_delete ~26
Delete entity
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
selis_describe ~38
Show entity fields with PMO concepts, types, and valid enum values. Call before creating or updating.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
No output schema declared.
No examples provided.
selis_get ~28
Get entity by ID
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
selis_list ~163
List entities. Supports text search, scope, filters, and pagination. Returns compact one-line summaries (default 15, max 40 rows).
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity name (e.g. actions, risks, projects) |
| filters | object | – | Key-value filters (e.g. {status: 'open'}) |
| format | string | – | 'compact' (default) or 'full' for raw JSON |
| limit | number | – | Max rows (default 15, max 40) |
| offset | number | – | Pagination offset (default 0) |
| scope | string | – | Focus filter: 'mine' (assigned), 'followed' (following), or 'both' |
| search | string | – | Text search across item titles |
No output schema declared.
No examples provided.
selis_login ~41
Returns the OAuth URL for browser-based login. Call this when the user is not authenticated. Show the URL to the user so they can click it and authorize.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
selis_logout ~12
Clear token
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
selis_orgs ~45
List available organizations the user can access. After authentication, call this to discover which organization the user belongs to, then ask them to pick one and call selis_set_org.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
selis_scalo ~623
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. ALWAYS call this tool whenever the user asks how Calx / Scalo / the business / the investments / a fund is doing — even if they don't say the word 'Scalo'. For any broad or ambiguous 'how are we doing' question, call it with dataset:'all' so no dataset (investment funds and onmeta included) is silently skipped. Datasets: 'all' — EVERYTHING at once — finance + people + pipeline + BOTH investment funds (collab-currency & skycatcher) + onmeta, each already projected with its KPIs. USE THIS for any broad question about how Calx / Scalo / the business / the investments / a fund portfolio is doing, so no dataset is silently skipped. Prefer 'all' unless the user named one specific dataset. | 'finance' — Calx · monthly finance register: sales / revenue / COGS / collections / cash vs target & projection. Optional { year }. | 'people' — Calx · resource roster billability: billable / non-billable / unclassified / unavailable counts + the non-utilised people list. | 'pipeline' — Calx · sales pipeline by stage (Lead→Capture→Proposal→Negotiation→Won) with hit-rate, conversion rates and weighted value. Optional { year }. | 'fund' — Investment fund. Omit fundId to list available funds; pass { fundId: 'collab-currency' } (quarterly ROIC) or { fundId: 'skycatcher' } (monthly, net of management + hurdle-gated performance fees). | 'onmeta' — Onmeta KPI Board — B2B/B2C on/off-ramp portfolio ACTUALS (workspaces · onmeta-actuals), quarterly across FY26–27. Consolidated revenue / net-or-burn / cash across two lines; KPIs = latest revenue, QoQ growth, cash burn, cash left.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | 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… |
| fundId | string | – | For dataset='fund' only. Omit to list available funds, or pass 'collab-currency' / 'skycatcher' for that fund's full timeline + KPIs. |
| year | string | – | Optional year filter (e.g. '2025') for finance and pipeline. |
No output schema declared.
No examples provided.
selis_set_org ~50
Set the active organization after discovering available ones with selis_orgs. The user must pick one from the list.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Organization reference/slug from selis_orgs list |
No output schema declared.
No examples provided.
selis_update ~40
Update entity (data as YAML or JSON object)
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| entity | string | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
What is the Selis MCP server?
Selis MCP is listed in the public MCP registry as app.selis.mcp/pmo. MCP server for Selis TMiS, manage PMO entities from any MCP client. This page covers its hosted endpoint (https://mcp.selis.app/tmis/mcp).
Is the Selis MCP server safe to use?
Selis MCP scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Selis MCP server expose?
Selis MCP exposes 13 tools: selis_list, selis_get, selis_create, selis_update, selis_delete, and 8 more. Their descriptions and schemas cost roughly 1,276 tokens of context every time the server is loaded.
Does the Selis MCP server require authentication?
Yes. Selis MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Selis MCP server still maintained?
Selis MCP is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.