mdfromx.com
Finalizing the report
Preparing the stored Is Agentic score
mdfromx.com
Preparing the stored Is Agentic score
mdfromx.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 17 applicable checks
Strong
Weighted across 12 applicable checks
Strong
Weighted across 3 applicable checks
Strong
Weighted across 3 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
Checks are grouped by relevance for App sites.
Homepage: 8139 chars, semantic headings (1 H1 + 6 H2s + 23 H3s), 23.8% content ratio. 5 of 5 sampled inner pages have text without JavaScript.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 15 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
OpenAPI spec found at https://mdfromx.com/openapi.json (version: 3.1.0)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Zero-auth service - documented as open with no authentication required, and API operations responded without credentials
Zero-auth service - no scoping needed, all endpoints are openly accessible to agents
API returns JSON error responses (400 at GET https://mdfromx.com/api/v1/posts, an operation in the OpenAPI spec)
MCP server exposes 5 resource(s) via resources/list
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://mdfromx.com/sitemap.xml with 24 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
Pricing page found at /pricing
API/docs link found on homepage and resolves: /docs
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 9 measured pages fit an agent context budget (largest ~2K tokens)
REST API documentation found at https://mdfromx.com/docs/agents. Best-of-protocols score: 7/7.
Zero-friction onboarding verified live: keyless API surface fetched without credentials - no signup step exists
MCP server connected via Streamable HTTP - io.github.pc-style/x-md v1.2.0 (protocol 2025-11-25)
The live API operation https://mdfromx.com/api/v1/posts returns IETF RateLimit headers: ratelimit, ratelimit-limit, ratelimit-policy.
OpenAPI uses application/problem+json (RFC 7807) for 4xx/5xx responses
API versioning strategy found (URL versioning) with sunset/deprecation markers documented
No CLI tool found
How to pass
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
100% of operations define typed response schemas, 100% use application/json
REST: agent-friendly schema (18 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 18/18 ops with IDs, 18/18 with typed schemas
5/5 resources read with valid mimeType and non-empty content
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 7/7 entries, trustManifest present
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 7/7 entries
All 7 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
trustManifest present on catalog entries (7/7 entries valid, catalog at /.well-known/ard.json)
In a search for your API docs, none of the 10 results is your official docs. In a search for your MCP server, SDK or CLI, we found your MCP server at #1 (https://mdfromx.com/docs/mcp)
How to pass
Make sure a web search for your product's API docs returns your own docs page, and a search for your MCP server, SDK or CLI returns your own pages for those tools. Keep docs on your own domain or a subdomain, or link your docs site from your homepage or llms.txt, give each tool its own page (for example /mcp) with the tool name in the title, put your product name and "API" in the docs title and main heading, and link your GitHub org from your homepage.
NPM package found: mdfromx - "Typed TypeScript and Effect client for the mdfromx (x.md) API: X posts, profiles and search as JSON or Markdown"
MCP manifest has full branding (name, icon, description) at /.well-known/mcp/server-card.json
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 4 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "import-x-history" (skill-md); 3 other skills present; not fetched
A2A Agent Card found: "x.md"
4 official skills published on skills.sh (skills.sh/pc-style)
Structured pricing.md found at /pricing.md (73 lines)
MCP server discoverable via server-card.json at /.well-known/mcp/
Rich agent mode view at ?mode=agent with 5 agent signals and navigation links
RFC 8288 Link header advertises: describedby, service-desc, api-catalog, alternate(markdown)
Full markdown fallback support. Homepage (https://mdfromx.com/index.md) and all 3 sampled content pages return markdown: https://mdfromx.com/about.md, https://mdfromx.com/docs.md, https://mdfromx.com/docs/pagination.md
100% of 24 sampled sitemap entries carry lastmod; newest is 33 day(s) old
Found the llms.txt at https://mdfromx.com/llms.txt.
The llms.txt is well-formatted: 67 lines with markdown links, 7,320 characters in total.
Agent Skill "import-x-history" says when to use it at /.well-known/agent-skills/index.json - description: "Use when onboarding a user from their X handle, building a writing-style or memory profile..."
4 installable skills with well-formed SKILL.md manifests (4/4 carry name + description). Agents can understand capabilities in depth
Entity linking to github.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
Rich schema vocabulary: BreadcrumbList, Service, FAQPage
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://mdfromx.com/index.md serves markdown
Frontmatter with title + description, canonical, and last-updated on /agents.md
Code fences balanced across 2 markdown documents
Developer portal found at /developers
RFC 9727 api-catalog with 3 API link(s) and rfc9727 profile
Path-suffix markdown docs served with text/markdown content-type: /agents.md, /auth.md, /index.md
All 7 tools on product MCP have detailed descriptions (>= 20 chars)
7/7 tools on product MCP have parameter schemas, 6 with required fields
product MCP identifies as "io.github.pc-style/x-md" v1.2.0 with instructions
product MCP exposes 7 tools - substantial tool surface
All 7 tool names follow consistent convention, descriptive, and non-generic
WorkOS auth.md structure at https://mdfromx.com/auth.md - 6/8 walkthrough sections (found Discover, Pick a method, Register, Claim, Errors, and Revocation); anchors: oauth-protected-resource, oauth-authorization-server, and agent_auth
product MCP returns structured JSON-RPC errors with code and message
product MCP uses modern Streamable HTTP transport
Cursor-based pagination found in OpenAPI spec response schemas or query parameters
SDK package found only in npm
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
product MCP: 7/7 tools have behavioral annotations (readOnlyHint/destructiveHint)
MCP server card found at https://mdfromx.com/.well-known/mcp/server-card.json (server-card extension, all required fields)
Batch/bulk operations mentioned at https://mdfromx.com/agents.md but no formal OpenAPI definition found
How to pass
Offer a batch endpoint that accepts an array of operations in one request, documented in your spec, so an agent acting on many items can do it in bulk instead of looping one call at a time.
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
50 native controls, 0 non-native div-soup affordances (100% native).
49/49 interactive elements have a computable accessible name (100%).
1/1 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does mdfromx.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does mdfromx.com do and who is it for? Explain it back to me.
3 steps1 reasoning step
The agent successfully retrieved and synthesized the core positioning, pricing, and use-case information from two fetched pages (homepage and docs), but encountered significant gaps in rate-limit specifics, upstream provider identity, and service sustainability that the site does not expose in a complete form.