com.themonexus/terminal
REMOTE · TERMINAL.THEMONEXUS.COM · SCANNED SEP 22
Live geopolitical and markets intelligence wire: 35k+ wire items, event threads, 55k+ articles.
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 → Why this is hard to score →
Endpoint Security66
- 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 27 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1734 tokens (~64/item across 27 items; 27 tools + 0 resources), lean.Pass
- 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 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
- We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 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
How do I install the com.themonexus/terminal MCP server?
com.themonexus/terminal is a hosted endpoint at https://terminal.themonexus.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 · terminal.themonexus.com
claude mcp add --transport http com-themonexus-terminal 'https://terminal.themonexus.com/mcp'
{
"mcpServers": {
"com-themonexus-terminal": {
"url": "https://terminal.themonexus.com/mcp"
}
}
} {
"servers": {
"com-themonexus-terminal": {
"type": "http",
"url": "https://terminal.themonexus.com/mcp"
}
}
} [mcp_servers.com-themonexus-terminal] url = "https://terminal.themonexus.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-themonexus-terminal": {
"type": "remote",
"url": "https://terminal.themonexus.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-themonexus-terminal --url 'https://terminal.themonexus.com/mcp' --transport streamable-http
mcp_servers:
com-themonexus-terminal:
url: "https://terminal.themonexus.com/mcp" {
"McpServers": {
"com-themonexus-terminal": {
"Transport": "http",
"Url": "https://terminal.themonexus.com/mcp"
}
}
} assistant mcp add com-themonexus-terminal -t streamable-http -u 'https://terminal.themonexus.com/mcp'
{
"mcpServers": {
"com-themonexus-terminal": {
"type": "http",
"url": "https://terminal.themonexus.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.
- 11 Sept 26 +54
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 27 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 10 Sept 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 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 +1
- Stability: 0.97 → pass security
- 13 Aug 26 0
- DNSSEC: fail → pass ▲ security
- 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
- 7 Aug 26 0
- Schema quality: 75 → 64 ▲ functional
- The server no longer declares the “experimental” capability functional
- New tool “agentpay” functional
- New tool “agentpay_latest” functional
- New tool “capex” functional
- New tool “capex_summary” functional
- New tool “catalogues” functional
- New tool “deals” functional
- New tool “deals_hot” functional
- New tool “deals_search” functional
- New tool “funding” functional
- New tool “funding_latest” functional
- New tool “funding_search” functional
- New tool “modelwatch” functional
- New tool “modelwatch_latest” functional
- New tool “modelwatch_search” functional
- New tool “transcripts_context” functional
- New tool “transcripts_episode” functional
- New tool “transcripts_search” functional
- New tool “transcripts_sentiment” functional
- New tool “verticals” functional
- New tool “verticals_latest” functional
- 4 Aug 26 0
- Server version: 1.28.1 → 1.29.0 functional
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 22 Sept 2026 · Probed https://terminal.themonexus.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=terminal.themonexus.com | CN=YE2,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6f36e01c1a8f29912ad85652381543958f3 |
| SANs: terminal.themonexus.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 terminal.themonexus.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| themonexus.com. | present | 2371 | 13 | Verified |
| terminal.themonexus.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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://terminal.themonexus.com/mcp | Verified | 200 | |
| http (plaintext) | http://terminal.themonexus.com/mcp | HTTPS enforced | 301 | https://terminal.themonexus.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. 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 →
agentpay ~59
Agentic-payments ecosystem brief: x402/MPP/USDC events with episode citations (paid, $0.002/req or pass). Args: limit: max events (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
agentpay_latest ~30
The single most recent agentic-payments event (paid, $0.001/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
capex ~91
AI-capex / model-economy metrics: raises, cloud growth, memory prices, token costs (paid, $0.002/req or pass). Args: metric: optional metric family filter (e.g. "cloud_growth", "memory_price", "capital_raise"). limit: max metrics (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| metric | string | – | – |
No output schema declared.
No examples provided.
capex_summary ~29
Metric families present in the capex tracker (paid, $0.001/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
catalogues ~54
In-date retailer catalogues from the PriceMate corpus (paid, $0.002/req or pass). Args: limit: max catalogues to return (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
deals ~112
Live in-date SADC deals from the PriceMate catalogue corpus (paid, $0.003/req or pass). Real retail prices across Botswana, Lesotho, Mozambique, Namibia and South Africa: microwaves, phones, appliances, groceries. Prices in local currency per retailer. Args: category: optional category filter (e.g. Electronics, Groceries, Appliances). limit: max deals to return (1-100).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
deals_hot ~53
Biggest absolute price drops among in-date SADC products (paid, $0.001/req or pass). Returns products where the retailer listed an old price, sorted by savings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
deals_search ~87
Search in-date SADC products by name or brand (paid, $0.005/req or pass). Args: q: search term, at least 2 characters (e.g. "airfryer", "iPhone 15", "OMO"). limit: max results (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
funding ~49
Funding/IPO events mined from the podcast corpus (paid, $0.005/req or pass). Args: limit: max events (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
funding_latest ~28
The single most recent funding/IPO event (paid, $0.002/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
funding_search ~71
Funding events by company name (paid, $0.003/req or pass). Args: company: company name fragment (e.g. "SpaceX", "Ambrook"). limit: max events (1-20).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_article ~51
One full licensed Monexus article as markdown plus metadata (paid, $0.01/req or pass). Args: slug: the article slug from list_articles.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_context ~59
Full context brief for a thread: background, timeline and significance (paid, $0.005/req or pass). Args: item_id: the thread/item id to build the context brief for.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
No output schema declared.
No examples provided.
get_thread ~58
One event thread with all of its wire items (paid, $0.002/req or pass). Args: thread_id: the thread id, as returned by list_threads or search_wire.
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | – |
No output schema declared.
No examples provided.
list_articles ~85
Index of 55,000+ licensed Monexus articles (paid, $0.002/req or pass). Args: category: optional category filter. limit: max articles to return. before: pagination cursor, return articles published before this timestamp/id.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | – |
| category | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_categories ~24
Beat/category scoreboard with item counts and latest timestamps (free, no key needed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_threads ~30
Live event threads: wire items clustered into developing stories (paid, $0.002/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
modelwatch ~58
Model-card watch: launches, silent downgrades, safeguards, policy events by lab (paid, $0.005/req or pass). Args: limit: max events (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
modelwatch_latest ~29
The most recent model-economy event (paid, $0.002/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
modelwatch_search ~76
Model-watch events by lab name (paid, $0.003/req or pass). Args: lab: lab name fragment (e.g. "Anthropic", "OpenAI", "Meta"). limit: max events (1-20).
| Name | Type | Req | Description |
|---|---|---|---|
| lab | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
search_wire ~96
Latest Monexus Terminal wire items (paid, $0.001/req or pass). Args: category: optional beat filter, e.g. geopolitics, business, tech, crypto, sports, science. query: optional full-text search string. limit: max items to return (1-100).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
transcripts_context ~63
Windowed context around a transcript segment (paid, $0.005/req or pass). Args: episode: episode id from transcripts_search. start: segment start time in seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| episode | string | yes | – |
| start | number | yes | – |
No output schema declared.
No examples provided.
transcripts_episode ~50
One podcast episode: metadata, segment count, opening (paid, $0.01/req or pass). Args: episode: episode id from transcripts_search.
| Name | Type | Req | Description |
|---|---|---|---|
| episode | string | yes | – |
No output schema declared.
No examples provided.
transcripts_search ~112
Search 368 episodes of a business/finance podcast corpus (paid, $0.002/req or pass). FTS-ranked segments with episode id, date and start time. Ideal for research agents that need quoted, dated business-news material. Args: q: search term, at least 3 characters (e.g. "stablecoin", "agentic payments"). limit: max results (1-20).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
transcripts_sentiment ~63
Lexicon sentiment over top matching segments (paid, $0.002/req or pass). Args: q: search term. limit: max segments scored (1-20).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
verticals ~61
Agent-commerce & messy-middle vertical intel: Shopify GMV, Ambrook, super.com datapoints (paid, $0.01/req or pass). Args: limit: max datapoints (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
verticals_latest ~30
The single most recent vertical-intel datapoint (paid, $0.002/req or pass).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.themonexus/terminal MCP server?
com.themonexus/terminal is an MCP server listed in the public MCP registry as com.themonexus/terminal. Live geopolitical and markets intelligence wire: 35k+ wire items, event threads, 55k+ articles. This page covers its hosted endpoint (https://terminal.themonexus.com/mcp).
Is the com.themonexus/terminal MCP server safe to use?
com.themonexus/terminal scores 80 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 com.themonexus/terminal MCP server expose?
com.themonexus/terminal exposes 27 tools: search_wire, list_threads, get_thread, get_context, list_articles, and 22 more. Their descriptions and schemas cost roughly 1,608 tokens of context every time the server is loaded.
Does the com.themonexus/terminal MCP server require authentication?
No. We connected to com.themonexus/terminal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.themonexus/terminal MCP server still maintained?
com.themonexus/terminal is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.