Home / MCP registry index / com.apievangelist/api-evangelist

com.apievangelist/api-evangelist

com.apievangelist/api-evangelist in the official MCP registry. Endpoint https://mcp.apievangelist.com/mcp. Source: github.com/api-evangelist/apievangelist-aws.

The registry describes it as: Sixteen years of API research as MCP tools — stories, areas, governance blocks & services

We read its 68 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_overview guide_topic find_services get_service find_solutions get_solution find_tools get_tool get_contact search_api_evangelist find_posts get_post find_areas get_area find_building_blocks get_building_block find_conversations get_conversation find_papers get_paper find_videos get_video get_timeline get_guidance_section find_vocabulary get_feeds find_tags get_tag find_related get_stats find_company_insights insights_dimensions insights_adoption get_company_insight company_gaps company_dimensions company_peers company_whitespace company_signals find_entities entity_demand find_measured_standards standard_adoption standard_coalition standard_repositories validate_api api_coverage reconcile_waivers governance_report verify_certificate classify_api_fields diff_api_versions api_scorecard govern_estate deprecation_posture validate_onboarding certify_api export_agent_rules audit_pipeline forge_mcp_tools and 8 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-apievangelist-api-evangelist/badge.svg)](https://lazaretto.dev/mcp-registry/com-apievangelist-api-evangelist)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.