Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
API Evangelist is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
67
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Sixteen years of API research as MCP tools — stories, areas, governance blocks & services
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http api-evangelist-mcp https://mcp.apievangelist.com/mcp
# 2 — ask your agent for something these tools do
# get_overview, guide_topic, find_services and 64 more
API Evangelist costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
APAll 1 server
apievangelist1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http api-evangelist-mcp https://mcp.apievangelist.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
67 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
START HERE. What the API Evangelist network offers: sixteen years of API research as searchable stories, 77 topic areas, governance building blocks (guidance, rules, policies, standards, strategies), papers, conversations, and the consulting services Kin Lane offers teams. Returns counts, entry points, and how to engage.
No parameter schema on file.
PRO — Curated guide to one API topic (e.g. "gateways", "api governance", "discovery", "agents"). Bundles the matching topic area (with related areas), top guidance, rules, policies, and standards, relevant papers and recent stories, plus the API Evangelist services that can help a team with this topic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | The topic to build a guide for. |
The services API Evangelist offers teams and customers — API strategy, governance, discovery, and evangelism engagements by Kin Lane. The front door to working with API Evangelist. (For the third-party vendor registry, use find_solutions.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
Full detail for one service offering by slug; include=["content"] inlines the full pitch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| include | array | no | — |
The solutions registry — 740+ third-party API services and tools (gateways, portals, testing, monitoring, …) ranked by adoption across the companies API Evangelist tracks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One solution from the vendor registry by slug, with its website and adoption count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
The open-source tooling registry — 400+ tools in use across the companies API Evangelist tracks, each with adoption counts and technology-radar placement.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One tool from the tooling registry by slug, with its website, adoption count, and radar ring.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Every way to reach API Evangelist — email, contact form, newsletter, GitHub, social channels, and postal mail.
No parameter schema on file.
Unified search across the whole network: 5k+ stories, 77 topic areas, 2.5k governance building blocks, papers, conversations, videos, tools, timelines, services, and vocabulary. Filter with types (posts, areas, guidance, rules, policies, standards, strategies, schema, properties, experiences, lifecycle, conversations, videos, papers, services, solutions, tools, timelines, vocabulary).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| types | array | no | — |
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
Search or browse 5,100+ API Evangelist stories (2010–present); filter by year or tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | no | — |
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One story by slug (YYYY-MM-DD-slug); include=["content"] returns the full markdown body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| include | array | no | — |
The 77 focused topic areas of the network (agents, gateways, security, …), each a subsite with its own catalog.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One topic area with its related-area graph resolved — walk the network from here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Search the governance building blocks by type: guidance (177), rules (617), policies (283), standards (432), strategies (75), schema (11), properties (790), experiences (46), lifecycle (29).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One building block by type + slug; include=["content"] returns the full body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| slug | string | yes | — |
| include | array | no | — |
API Evangelist Conversations — recorded discussions with API practitioners (guest, company, YouTube/SoundCloud links).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One conversation with guest detail and media links; include=["content"] returns the writeup.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| include | array | no | — |
API Evangelist papers — single-PDF deep dives on one practice or topic, with outlines.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One paper with its full outline and purchase/landing URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
The API Evangelist video library — interviews and discussions from across the API space, searchable by transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One video by slug with its YouTube id; include=["content"] returns the full transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| include | array | no | — |
One of the four research timelines in chronological order: api (the moments that shaped web APIs), resources (which digital resources became APIs and when), industries (the industrial history framing API infrastructure), people (the people who made compute and APIs possible).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timeline | string | yes | — |
| page | integer | no | — |
| limit | integer | no | — |
One editorial guidance section as a list: history, technology, business, politics, governance, or evangelism — the six lenses API Evangelist organizes guidance through.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | yes | — |
| page | integer | no | — |
| limit | integer | no | — |
The API vocabulary — thousands of resources, actions, personas, domains, schemas, and tags extracted from the API landscape. Filter by category.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| q | string | no | Free text over title, summary, tags, and body. |
| tags | array | no | Tag slugs; match any by default. |
| match | string | no | — |
| sort | string | no | — |
| fields | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
The static machine-readable feeds every network site publishes (JSON, APIs.json, zero-auth) — the no-key alternative to this API.
No parameter schema on file.
Browse and rank the network tag taxonomy — every subject tag across 16k+ docs, by frequency or breadth (how many content types use it). Search with q. The map of what API Evangelist covers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | — |
| sort | string | no | — |
| page | integer | no | — |
| limit | integer | no | — |
One tag with its per-type counts and everything it labels across the whole network (stories, areas, guidance, papers, …). Filter with types.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| types | array | no | — |
| page | integer | no | — |
| limit | integer | no | — |
Given any doc (type + slug), the most related content across the whole network, ranked by shared-tag relevance (rare, specific tags weigh most). "More like this," across stories, areas, guidance, papers, conversations, and more.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| slug | string | yes | — |
| types | array | no | — |
| limit | integer | no | — |
PRO — catalog intelligence: per-type counts, stories-per-year, and the top tags by reach across the network.
No parameter schema on file.
Browse profiled companies (Fortune 1000 + API providers) by name; ranked by technology-readiness signal. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | — |
| page | integer | no | — |
| limit | integer | no | — |
Cross-section ranking of the 40 tracked investment dimensions (AI, cloud, governance, …) by company signal. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | — |
| limit | integer | no | — |
Services, tools, or standards ranked by how many companies adopt them. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | — |
| page | integer | no | — |
| limit | integer | no | — |
Full demand-side profile for one company: 40-dimension readiness, adopted stack, per-quarter history. Pro.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
A company's weakest investment dimensions — where it is thin. Pro.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
PRO — a company's investment dimensions, each read AGAINST the measured cohort: the cohort median, mean and max, this company's rank and percentile, and an index where 1.0 is exactly typical. A raw dimension score is unreadable on its own; these are the columns that make it mean something.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
PRO — the companies most comparable to this one (same sub-sector where the data supports it, same industry otherwise), each with signal totals and top dimensions. The response says which basis it used.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| limit | integer | no | — |
PRO — what this company's peers run that it does not, ranked by how many peers carry it. The opening list for a vendor selling into the account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| limit | integer | no | — |
PRO — the company's adopted stack entity by entity (services, tools, standards), each with how many companies across the cohort carry it and its radar ring.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Browse the demand-side entity catalog — every service, tool and standard companies are measured against, ranked by how many carry it. Free. This is the left-hand side of the inversion: pick an entity here, then call entity_demand to see WHO.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
| q | string | no | Substring match on the entity name. |
| min_companies | integer | no | Only entities carried by at least this many companies. |
| page | integer | no | — |
| limit | integer | no | — |
PRO — THE INVERSION. Every other insights tool runs company -> stack; this one runs stack -> companies: which companies show demand for a given service, tool or standard, broken down by industry. This is the prospecting query — "who should I be selling this to" — and it exists in no report, bundle or page. Returns BOTH the authoritative company count and the companies it can actually name, with th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| slug | string | yes | Entity slug or display name — either resolves ("spark" and "Apache Spark" both work). |
| industry | string | no | Restrict the named companies to one industry. |
| limit | integer | no | — |
The standards bodies API Evangelist has actually MEASURED — repositories, maturity, governance, coalition. Distinct from find_standards, which searches 613 catalog entries describing what a standard IS. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | — |
| limit | integer | no | — |
How far a standards body actually got: repositories published, how many graduated past unclassified and the resulting share, release cadence, contributor count — with the provenance of every figure and an explicit list of what is NOT measured. Free, because a specification is a public good.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Who is actually behind a standard: the governing bodies and their membership, the working groups, the member companies, and the named people. Carries the caveats where our machine-readable source disagrees with the body's own published roster. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
Every repository a standards body publishes, with maturity, stars, forks, open issues and archived status. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| page | integer | no | — |
| limit | integer | no | — |
Lint an OpenAPI, AsyncAPI, Arazzo, or JSON Schema document against the curated best-of-breed ruleset (Spectral) and return the findings. Pass your own ruleset to run rules you own instead of the catalog — which is what you should do before gating on anything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Measure how much of an API description your governance actually inspects — coverage by section, each rule's reach, and the rules that match nothing. Like test coverage, one altitude up.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Reconcile a waivers file against lint output: suppress sanctioned violations and surface the expired, stale, and expiring ones. Returns the effective failing set a build should gate on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| waivers | string/object | yes | The waivers file to reconcile — sanctioned violations, with expiry. |
| violations | array/object/string | yes | Lint output to reconcile against the waivers. An array of findings, or the object a linter returned. |
Turn Spectral findings into a self-contained HTML governance report — severity summary, grouped by rule, framed toward progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| results | array/object | yes | Spectral findings to render. An array, or the { results: [...] } object a run returned. |
Re-verify a governance certificate against the API it attests to. If the API drifted or the certificate was forged, verification fails.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| certificate | string/object | yes | The governance certificate to re-verify. Alias: cert. |
| api | string/object | yes | The API description being attested or verified. String or parsed object. |
Inventory the PII, secret, and sensitive fields an OpenAPI exposes, across parameters and request/response schemas. Run this before exposing an API to agents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Compare two OpenAPI versions and classify every change as breaking, non-breaking, or an addition — at path, operation, parameter, request-body, and response granularity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| old | string/object | yes | The BASELINE version of the document. Aliases: from, base. |
| new | string/object | yes | The CANDIDATE version to compare against the baseline. Aliases: to, revision. |
Score an API's maturity 0-100 with a letter grade across design, governance coverage, documentation, and (from an apis.json) discoverability, agent-readiness, and operations. Pass your own ruleset — a score against rules you never adopted means little.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
PRO — Run the core governance checks across a WHOLE SET of internal APIs and roll them up: per-API score/grade/errors/PII, plus estate aggregates (avg score, grade distribution, APIs with PII/secrets) and a worst-first punch-list of what to fix. Pass apis ([{id, document}]) and your own ruleset. detail:true adds per-API dimensions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| apis | array | yes | The estate: one entry per API, [{ id, document }]. document alone is accepted for a single API. |
Report every deprecated operation and whether it actually announces a sunset. The ones that go quiet are the ones that break consumers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Validate an API Onboarding Descriptor (AID) against the api-commons schema and report which optional sections it fills in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| descriptor | string/object | yes | An API Onboarding Descriptor (AID) to validate. Aliases: aid, document. |
Issue a tamper-evident governance certificate attesting an API passed a named ruleset at a profile threshold. A SHA-256 fingerprint lets anyone re-verify it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api | string/object | yes | The API description being attested or verified. String or parsed object. |
Turn a governance ruleset into agent-native guidance — an AGENTS.md block, a system-prompt set, a per-rule remediation pack, and a digest — so agents follow the rules while authoring, not after linting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ruleset | object | yes | A Spectral ruleset to run instead of the catalog default. Score against rules you never adopted means little — pass your own. |
Score a repository's Spectral CI setup against an 8-point maturity rubric and return a prioritized punch-list. Pass a public repo ("owner/name") or files.
No parameter schema on file.
From an OpenAPI, forge an MCP server design, per-operation tools, Agent Skills, an enriched OpenAPI, a server.json, and apis.json properties.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Choose which operations and fields an API exposes to agents and emit a governed Tyk OpenAPI, an MCP tool manifest, and a Spectral ruleset with PII and secret checks.
No parameter schema on file.
Apply an OpenAPI Overlay to a document and report what each action matched. Use it for deprecation and migration choreography without forking the contract.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
| overlay | string/object | yes | An OpenAPI Overlay document whose actions are applied to document. |
Generate an example request and success-response payload for every operation from its schema.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Generate runnable curl, JavaScript, and Python samples for every operation, with path params filled in and a realistic body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string/object | yes | The API description to operate on — OpenAPI, AsyncAPI, Arazzo or JSON Schema. A YAML/JSON string or an already-parsed object; both are accepted. |
Score how reusable a set of APIs is and detect duplication across them — the anti-sprawl view of an estate.
No parameter schema on file.
Map each REST operation to its MCP tool and Agent Skill — the API -> MCP -> Agent-Skill chain — from an APIs.json, with a free/paid coverage scorecard and a flow map.
No parameter schema on file.
Generate an API's llms.txt and an AGENTS.md consumption contract — base URL, auth, the operation table, deprecated operations to avoid, and usage rules.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install API Evangelist or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish API Evangelist can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.