Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ITEON MCP Server

REMOTE · API.ITEON.PL · 2 COMPONENTS · SCANNED SEP 21

Polski software house B2B: 5 public + 7 OAuth 2.1 private MCP tools (AI estimate, draft, risk).

0 this week 88 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 649 tokens (~129/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the ITEON MCP Server server?

ITEON MCP Server is a hosted endpoint at https://api.iteon.pl/api/v1/mcp/public, 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 · api.iteon.pl

# add to Claude Code
claude mcp add --transport http pl-iteon-mcp 'https://api.iteon.pl/api/v1/mcp/public'
// .cursor/mcp.json
{
  "mcpServers": {
    "pl-iteon-mcp": {
      "url": "https://api.iteon.pl/api/v1/mcp/public"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pl-iteon-mcp": {
      "type": "http",
      "url": "https://api.iteon.pl/api/v1/mcp/public"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pl-iteon-mcp]
url = "https://api.iteon.pl/api/v1/mcp/public"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pl-iteon-mcp": {
      "type": "remote",
      "url": "https://api.iteon.pl/api/v1/mcp/public",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pl-iteon-mcp --url 'https://api.iteon.pl/api/v1/mcp/public' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pl-iteon-mcp:
    url: "https://api.iteon.pl/api/v1/mcp/public"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pl-iteon-mcp": {
      "Transport": "http",
      "Url": "https://api.iteon.pl/api/v1/mcp/public"
    }
  }
}
# add to Vellum
assistant mcp add pl-iteon-mcp -t streamable-http -u 'https://api.iteon.pl/api/v1/mcp/public'
// mcp.json
{
  "mcpServers": {
    "pl-iteon-mcp": {
      "type": "http",
      "url": "https://api.iteon.pl/api/v1/mcp/public"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 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
  • 27 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 21 Sept 2026 · Probed https://api.iteon.pl/api/v1/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=iteon.pl CN=WE1,O=Google Trust Services,C=US 14 Aug 2026 12 Nov 2026 ECDSA 256 ECDSA-SHA256 110a27d786d2c26a133a8f3e5b2a5224
SANs: iteon.pl, *.iteon.pl
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.iteon.pl. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
iteon.pl. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self';base-uri 'self';font-src 'self' data:;form-action 'self' https://login.microsoftonline.com https://appleid.apple.com;frame-ancestors 'self';img-src 'self' data: https:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' 'nonce-iuqSJGjH1mvf0ix5uFwRkA==';upgrade-insecure-requests;connect-src 'self' https://login.microsoftonline.com https://login.live.com https://appleid.apple.com https://*.ingest.sentry.io wss://app.iteon.pl wss://api.iteon.pl;frame-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.iteon.pl/api/v1/mcp/public Verified 200
http (plaintext) http://api.iteon.pl/api/v1/mcp/public HTTPS enforced 301 https://api.iteon.pl/api/v1/mcp/public
MCP tools · 5 exposed · ~591 tokens

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 →

Tool Tokens
case_studies.find_relevant ~175

Find ITEON real-world case studies (banking, insurance, government, custom apps, mobile, e-commerce, energy) matching a topic, technology, or industry. Use when user asks "who can build X" or "anyone done Y before". Returns 1-3 actual ITEON projects from portfolio with stack, period, outcomes, and link to full case study on iteon.pl.

NameTypeReqDescription
industrystringOptional industry filter: banking, insurance, government, fintech, energy, retail, agriculture, consumer.
limitnumberMax results (1-10, default 3).
querystringyesTopic, technology, or keywords (e.g. "Java legacy migration", "React Native mobile", ".NET Core API integration", "ECM banking").

No output schema declared.

No examples provided.

expert_match.find ~136

Find an ITEON expert with relevant skills for a specific technical problem. Returns name, role, specializations, years of experience, LinkedIn profile. Use when the user wants to know "who at ITEON can help with X". Personalizes the sales touch -- client knows who they will talk to.

NameTypeReqDescription
limitnumberMax results (1-5, default 2).
senioritystringOptional: required seniority level.
topicstringyesTechnical topic or problem (e.g. "microservices migration", "React Native iOS", "PostgreSQL multi-tenant").

No output schema declared.

No examples provided.

methodology.lookup ~95

Search ITEON public methodology, architectural patterns, blog posts, and case studies. Read-only public knowledge base. Use when the user asks technical/architectural questions and you want to cite professional sources.

NameTypeReqDescription
limitnumberMax results (1-10, default 3).
querystringyesTopic or keywords to search (e.g. "multi-tenant SaaS", "OAuth", "legacy modernization").

No output schema declared.

No examples provided.

stack.health_audit ~125

Run an objective health audit of a public URL: Google Lighthouse scores (performance, accessibility, SEO, best practices), HTTPS certificate validity, and security headers (HSTS, CSP, X-Frame-Options, Referrer-Policy). Returns hard data only -- ITEON has zero opinion in the response. Useful when the user wants to know "is my site healthy" before considering modernization.

NameTypeReqDescription
strategystringAudit strategy. Default: mobile.
urlstringyesHTTPS URL of the page to audit (e.g. "https://example.com").

No output schema declared.

No examples provided.

system.status ~60

Get current health status of the ITEON MCP server and platform. Returns overall status (operational/degraded/incident), version, deploy info, and per-component health (database, redis, queue). Use BEFORE calling private tools to verify service is available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the ITEON MCP Server server?

ITEON MCP Server is listed in the public MCP registry as pl.iteon/mcp. Polski software house B2B: 5 public + 7 OAuth 2.1 private MCP tools (AI estimate, draft, risk). This page covers its hosted endpoint (https://api.iteon.pl/api/v1/mcp/public).

Is the ITEON MCP Server server safe to use?

ITEON MCP Server scores 88 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 ITEON MCP Server server expose?

ITEON MCP Server exposes 5 tools: methodology.lookup, case_studies.find_relevant, expert_match.find, stack.health_audit, system.status. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.

Does the ITEON MCP Server server require authentication?

No. We connected to ITEON MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ITEON MCP Server server still maintained?

ITEON MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.