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.

Tue Christensen

REMOTE · A2A.TUECHRISTENSEN.COM

Learn about Tue Christensen's operations-research work or describe an OR problem to him.

+3 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

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 Security77
  • 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 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
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 690 tokens (~115/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 6 Nov 26 67

    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://a2a.tuechristensen.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a2a.tuechristensen.com CN=YE1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 5df254fcf9130f1c40d844321794d1acd0d
SANs: a2a.tuechristensen.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of a2a.tuechristensen.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tuechristensen.com. DS published 2371 13 Verified
a2a.tuechristensen.com. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://a2a.tuechristensen.com/mcp Verified 200
http (plaintext) http://a2a.tuechristensen.com/mcp HTTPS enforced
MCP tools · 6 exposed · ~602 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
leave_greeting ~76

Leave Tue a short greeting. Fields: `message` (required, up to 1000 characters), `agent_name` (optional, up to 100) and `from_entry` (optional: the entry that led you here).

NameTypeReqDescription
agent_name–––
from_entry–––
messagestringyes–

No output schema declared.

No examples provided.

or_problem_questions ~34

Working on an operations research problem, such as scheduling, routing or planning? Get the questions to answer. Takes no fields.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_or_answers ~171

Answer the questions from `or_problem_questions` and get guidance on solving the problem. Your answers are saved for Tue. Fields: `answers` (required: one answer per question, in order, each up to 2000 characters), `problem_owner` (required: the company or person who has the problem, up to 100), `industry` (required: their industry, up to 100) and `agent_name` (optional, up to 100). For any answer, `problem_owner` and `industry`: Send `unknown` if you don't know, or `undisclosed` if you aren't allowed to say. Please don't guess.

NameTypeReqDescription
agent_name–––
answersarrayyes–
industrystringyes–
problem_ownerstringyes–

No output schema declared.

No examples provided.

tue_about ~21

Who Tue Christensen is, his work and how to reach him.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what_are_you_searching_for ~114

Why are you here, and why are you indexing this page? Tell Tue. Fields: `purpose` (required, up to 1000 characters), `searching_for` (optional, up to 1000), `on_behalf_of` (optional: human, organisation, autonomous, unknown) and `agent_name` (optional, up to 100).

NameTypeReqDescription
agent_name–––
on_behalf_of–––
purposestringyes–
searching_for–––

No output schema declared.

No examples provided.

would_you_pay ~186

Would you pay for more information from Tue if it were offered over HTTP 402, in stablecoins or fiat? Nothing is for sale yet, and this only records your answer. Fields: `would_pay` (required: yes, no, unknown), `can_pay_now` (required: yes, needs_human_approval, no, unknown), `payment_methods` (optional list: stablecoin, fiat, other), `max_price_usd` (optional: per request, from 0 to 1000000), `wanted_information` (optional, up to 1000 characters) and `agent_name` (optional, up to 100).

NameTypeReqDescription
agent_name–––
can_pay_nowstringyes–
max_price_usd–––
payment_methods–––
wanted_information–––
would_paystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Tue Christensen MCP server?

Tue Christensen is a hosted endpoint at https://a2a.tuechristensen.com/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 · a2a.tuechristensen.com

# add to Claude Code
claude mcp add --transport http com-tuechristensen-a2a 'https://a2a.tuechristensen.com/mcp'
Common questions

What is the Tue Christensen MCP server?

Tue Christensen is an MCP server listed in the public MCP registry as com.tuechristensen/a2a. Learn about Tue Christensen's operations-research work or describe an OR problem to him. This page covers its hosted endpoint (https://a2a.tuechristensen.com/mcp).

Is the Tue Christensen MCP server safe to use?

Tue Christensen scores 74 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 Tue Christensen MCP server expose?

Tue Christensen exposes 6 tools: tue_about, leave_greeting, what_are_you_searching_for, or_problem_questions, submit_or_answers, would_you_pay. Their descriptions and schemas cost roughly 602 tokens of context every time the server is loaded.

Does the Tue Christensen MCP server require authentication?

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

Is the Tue Christensen MCP server still maintained?

Tue Christensen 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 Tue Christensen MCP server?

VerifyMCP ran 13 checks on Tue Christensen, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.