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.

Thomas Anglero Speaker MCP

REMOTE · ANGLERO.COM · SCANNED SEP 28

Thomas Anglero, Strategic AI Advisor & keynote speaker: bio, topics, booking, inquiry tools.

Available components

+3 this week 71 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 Security60
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 481 tokens (~96/item across 5 items; 5 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 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_speaking_inquiry" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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 Thomas Anglero Speaker MCP server?

Thomas Anglero Speaker MCP is a hosted endpoint at https://anglero.com/wp-json/agent/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 · anglero.com

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

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.

  • 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
  • 27 Sept 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.

  • 25 Sept 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
  • 23 Sept 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.

  • 22 Sept 26 0
    • Tool “submit_speaking_inquiry” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • “submit_speaking_inquiry” reworded the description of “company” cosmetic
  • 20 Sept 26 +1

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

  • 18 Sept 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.

  • 16 Sept 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.

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 28 Sept 2026 · Probed https://anglero.com/wp-json/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=anglero.com CN=YE1,O=Let's Encrypt,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA384 6567295950ba169fc7a81753ab895676d6e
SANs: anglero.com, www.anglero.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 anglero.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
anglero.com. present 2371 13 Verified
anglero.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
Header Value
content-security-policy upgrade-insecure-requests
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://anglero.com/wp-json/agent/mcp Verified 200
http (plaintext) http://anglero.com/wp-json/agent/mcp HTTPS enforced 301 https://anglero.com/wp-json/agent/mcp
MCP tools · 5 exposed · ~442 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
get_availability_guidance ~37

How availability is confirmed. No live calendar is published. Availability for a date is confirmed on inquiry, typically within two business days.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_booking_info ~41

How booking works, the formats offered, and how fees are handled. Fees are provided on inquiry, tailored to format and location. Response within two business days.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_speaker_profile ~27

Canonical short bio, positioning, notable clients, and links for Thomas Anglero.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_speaking_topics ~28

The three keynote topics with titles, subtitles, and a one-paragraph description each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_speaking_inquiry ~309

Send a speaking inquiry to Thomas Anglero. Requires six fields: name, email, phone, company or organization, event date, and a free-text message. Fold every other detail into the message in natural language: what Thomas should speak about, event location, format (in person, virtual, or pre-recorded), expected audience size, your role, and budget if any. Writes into the same pipeline as the website form: it records the inquiry and sends the confirmation and notification emails. Thomas replies personally, typically within two business days.

NameTypeReqDescription
companystringyesThe company or organization the inquiry is on behalf of.
emailstringyesContact email address.
event_datestringyesEvent date, for example "17 February 2027". If the date is not yet fixed, give the intended month or timeframe.
messagestringyesA short free-text description of the event. Fold everything relevant into this one field in natural language: what you would like Thomas to speak about, event location, format (in person, virtual, or…
namestringyesFull name of the person making the inquiry.
phonestringyesContact phone number, including country code if the event is outside Norway.
websitestring–Leave blank. Anti-spam field.

No output schema declared.

No examples provided.

Common questions

What is the Thomas Anglero Speaker MCP server?

Thomas Anglero Speaker MCP is listed in the public MCP registry as com.anglero/speaker. Thomas Anglero, Strategic AI Advisor & keynote speaker: bio, topics, booking, inquiry tools. This page covers its hosted endpoint (https://anglero.com/wp-json/agent/mcp).

Is the Thomas Anglero Speaker MCP server safe to use?

Thomas Anglero Speaker MCP scores 71 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 Thomas Anglero Speaker MCP server expose?

Thomas Anglero Speaker MCP exposes 5 tools: get_speaker_profile, get_speaking_topics, get_booking_info, get_availability_guidance, submit_speaking_inquiry. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.

Does the Thomas Anglero Speaker MCP server require authentication?

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

Is the Thomas Anglero Speaker MCP server still maintained?

Thomas Anglero Speaker 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.