TwexAPI MCP server
io.twexapi/mcptwexapi.iostreamable-httpv1.1.1Scanned
Search X (Twitter) posts and read profiles, followers, trends and X Articles. OAuth sign-in.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TwexAPI MCP server can do
The TwexAPI MCP server is published by twexapi.io, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: twexapi_request), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Oct 21, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
twexapi_requestCall an allowed TwexAPI REST endpoint.No findings
Why it is in this group
- The name "twexapi_request" says "request": a word for a change.
Description, as the server wrote it Call an allowed TwexAPI REST endpoint.
Only reads 1Show 1 read-only tool
exploreSearch allowed TwexAPI endpoints.No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it Search allowed TwexAPI endpoints.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://api.twexapi.io/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata
- https://api.twexapi.io/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.twexapi.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Posture changes
- Oct 29, 2026
- Client ID metadata documents: no to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Client ID metadata documents: no -> yes.View diff
- Client ID metadata documents: no to yes
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http twexapi https://api.twexapi.io/mcpclaude mcp add --transport http twexapi https://api.twexapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__twexapi__explore"
],
"ask": [
"mcp__twexapi__twexapi_request"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as twexapi. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.twexapi/mcp/verify?hash=1dff45ce0407f663dd84f07dd17499b7df9f1553f0eb10b140ab1caf9d5b2012" | jq -e '.changed == false'Pinned hash 1dff45ce0407, from Oct 21, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.twexapi/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.twexapi/mcp)Source: MCP Registry. Synced Oct 27, 2026, 14:18 UTC.
TwexAPI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TwexAPI MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TwexAPI MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TwexAPI MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TwexAPI MCP server have?
- 2 tools: 1 write, 1 read. twexapi_request and explore.
Does the TwexAPI MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the TwexAPI MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TwexAPI MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.