mdfromx.com
https://mdfromx.com/api/mcp
active Production-safe Score 97/100 http no auth
At a glance
| Endpoint | https://mdfromx.com/api/mcp |
|---|---|
| Source | https://mdfromx.com/mcp |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-11 12:58:38 |
| Last checked | 2026-11-17 21:53:50 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 222 / 443 ms |
| Last successful check | 2026-11-17 21:53:50 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
x_md_get_post— Read one public X (formerly Twitter) post together with its thread and conversation context, as Markdown plus structured post objects. Accepx_md_get_profile— Read a public X profile — display name, bio, location, follower and following counts, join date, verification — together with that account’sx_md_search_posts— Search public X posts or accounts by keyword, phrase, hashtag, or X advanced-search operator such as from:, to:, since:, until:, and filter:x_md_get_followers— Page through the public followers of an X account, returning each follower’s handle, display name, bio, and counts. Use it to size or samplex_md_get_following— Page through the accounts a public X account follows, returning each one’s handle, display name, bio, and counts. Use it to map who an accoux_md_import_posts— Bulk-import a public X account’s posts over a date range, newest first, as raw post objects with every upstream field (the same contract assubmit_feedback— Send feedback about x.md to the x.md team. Use it to report bugs, request features, ask questions or share what worked well. Include the exa
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:53:50 | ✓ | ✓ | 200 ms | 94 | active |
| 2026-11-17 21:38:40 | ✓ | ✓ | 208 ms | 94 | active |
| 2026-11-17 21:23:22 | ✓ | ✓ | 191 ms | 94 | active |
| 2026-11-17 21:08:10 | ✓ | ✓ | 175 ms | 94 | active |
| 2026-11-17 20:53:06 | ✓ | ✓ | 331 ms | 91 | active |
| 2026-11-17 20:38:04 | ✓ | ✓ | 191 ms | 94 | active |
| 2026-11-17 20:22:59 | ✓ | ✓ | 177 ms | 94 | active |
| 2026-11-17 20:07:53 | ✓ | ✓ | 176 ms | 94 | active |
| 2026-11-17 19:52:02 | ✓ | ✓ | 179 ms | 94 | active |
| 2026-11-17 19:36:55 | ✓ | ✓ | 180 ms | 94 | active |
| 2026-11-17 19:21:44 | ✓ | ✓ | 344 ms | 91 | active |
| 2026-11-17 19:06:31 | ✓ | ✓ | 333 ms | 91 | active |
| 2026-11-17 18:51:18 | ✓ | ✓ | 378 ms | 91 | active |
| 2026-11-17 18:36:10 | ✓ | ✓ | 358 ms | 91 | active |
| 2026-11-17 18:21:06 | ✓ | ✓ | 341 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mdfromx.com/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mdfromx-com-api-mcp # JSON