Thomas Anglero Speaker MCP
REMOTE · ANGLERO.COM · SCANNED AUG 3
Thomas Anglero speaker MCP: bio, keynote topics, booking info, and speaking-inquiry submission.
Available components
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 →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 443 tokens (~88/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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · anglero.com
claude mcp add --transport http com-anglero-speaker https://anglero.com/mcp
[mcp_servers.com-anglero-speaker] url = "https://anglero.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-anglero-speaker": {
"type": "remote",
"url": "https://anglero.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-anglero-speaker --url https://anglero.com/mcp --transport streamable-http
mcp_servers:
com-anglero-speaker:
url: "https://anglero.com/mcp" {
"mcpServers": {
"com-anglero-speaker": {
"type": "http",
"url": "https://anglero.com/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.
- 3 Aug 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.
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 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.
- 27 Jul 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
- 26 Jul 26 65
First indexed and scored.
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 3 Aug 2026 · Probed https://anglero.com/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 Jul 2026 | 17 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 523ffd1e7e00afbe8aa3d125a79385088d7 |
| 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 |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://anglero.com/mcp | Verified | 200 | |
| http (plaintext) | http://anglero.com/mcp | HTTPS enforced | 301 | https://anglero.com/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.
get_availability_guidance 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 Get booking information ~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 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 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 Submit a speaking inquiry ~271
Send a speaking inquiry to Thomas Anglero. Requires four fields only: name, email, event date, and a free-text message. Fold every other detail into the message in natural language: event location, format (in person, virtual, or pre-recorded), the topic or theme, expected audience size, the organisation and 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Contact email address. | |
| event_date | string | yes | Event date, for example "17 February 2027". If the date is not yet fixed, give the intended month or timeframe. |
| message | string | yes | A short free-text description of the event. Fold everything relevant into this one field in natural language: event location, format (in person, virtual, or pre-recorded), the topic or theme you woul… |
| name | string | yes | Full name of the person making the inquiry. |
| website | string | — | Leave blank. Anti-spam field. |
No output schema declared.
No examples provided.