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.

DelegAIze Agent Check

REMOTE · DELEGAIZE.INNOV-AI-TIVE.DE

Agent check without sign-in: which AI agents would take over your recurring office work.

63 Trust /100

Last scanned (5 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security69
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 723 tokens (~361/item across 2 items; 2 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 63

    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 Nov 2026 · Probed https://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=innov-ai-tive.de CN=WE1,O=Google Trust Services,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 47bed0116bc68af413439f086ae48693
SANs: innov-ai-tive.de, delegaize.innov-ai-tive.de, *.delegaize.innov-ai-tive.de
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 delegaize.innov-ai-tive.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
innov-ai-tive.de. No DS 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
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(self "https://ai-call-bot.innov-ai-tive.de"), display-capture=(self), geolocation=(), usb=(), serial=(), bluetooth=(), hid=(), midi=(), payment=(), 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://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-mcp Verified 200
http (plaintext) http://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-mcp Served over HTTP 200
MCP tools · 2 exposed · ~611 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
agenten_check ~356

Returns the DelegAIze agent catalogue (what each agent does, its tools, minutes saved per item), the clustering rules, the agents that match the input by keyword, and a personal link (demo or free start) carrying utm and ref/pc. Input: EITHER beschreibung (the user's description of their work or one pasted mail) OR mail_uebersicht (subjects + sender domains, optionally a count per line, that YOUR mail tools collected — no bodies, no full addresses). No sign-in, nothing is stored, no data leaves for third parties. You do the reasoning: cluster with the rules, then present processes, agents and the estimated hours per month.

NameTypeReqDescription
beschreibungstring–Description of the work or one pasted mail (max 8000 chars).
mail_uebersichtarray–One entry per mail or per group of similar mails.
pcstring–Optional partner code from the user's link. Passed on to the sign-up/demo link.
refstring–Optional person code from the link the user came with (e.g. th, km). Passed on to the sign-up/demo link.
sprachestring––
tagenumber–How many days the mail summary covers (for the per-month estimate). Default 30.
utm_campaignstring–Optional campaign code.
utm_sourcestring–Optional, default 'mcp'.
variantestring–Campaign entry: backoffice (default), sap, maschinenbau, partner, verain (clubs), coachaize (studios), tekta (structures). sachverstaendige returns the trial case file link instead.

No output schema declared.

No examples provided.

agenten_check_mail ~255

Returns a link to the DelegAIze page where the user connects Gmail, Microsoft 365 or IMAP READ-ONLY. There the last 100 mails are clustered into recurring processes, 1-3 agents run live on them as drafts, and access is revoked or discarded right after. Use it when the user wants the check on their real mailbox but you have no mail tools, or prefers us to do the analysis. Explain that they must give consent on the page. Nothing happens until they open the link.

NameTypeReqDescription
pcstring–Optional partner code from the user's link. Passed on to the sign-up/demo link.
refstring–Optional person code from the link the user came with (e.g. th, km). Passed on to the sign-up/demo link.
sprachestring––
utm_campaignstring–Optional campaign code.
utm_sourcestring–Optional, default 'mcp'.
variantestring–Campaign entry: backoffice (default), sap, maschinenbau, partner, verain (clubs), coachaize (studios), tekta (structures). sachverstaendige returns the trial case file link instead.

No output schema declared.

No examples provided.

Install

How do I install the DelegAIze Agent Check MCP server?

DelegAIze Agent Check is a hosted endpoint at https://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-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 · delegaize.innov-ai-tive.de

# add to Claude Code
claude mcp add --transport http toasternet-delegaize-agenten-check 'https://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-mcp'
Common questions

What is the DelegAIze Agent Check MCP server?

DelegAIze Agent Check is an MCP server listed in the public MCP registry as io.github.toasternet/delegaize-agenten-check. Agent check without sign-in: which AI agents would take over your recurring office work. This page covers its hosted endpoint (https://delegaize.innov-ai-tive.de/api/sb/functions/v1/agenten-check-mcp).

Is the DelegAIze Agent Check MCP server safe to use?

DelegAIze Agent Check scores 63 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 DelegAIze Agent Check MCP server expose?

DelegAIze Agent Check exposes 2 tools: agenten_check, agenten_check_mail. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.

Does the DelegAIze Agent Check MCP server require authentication?

No. We connected to DelegAIze Agent Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DelegAIze Agent Check MCP server still maintained?

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

What did VerifyMCP test on the DelegAIze Agent Check MCP server?

VerifyMCP ran 12 checks on DelegAIze Agent Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about DelegAIze Agent Check: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.