MCP servers observed by Lowdown
ai.entityenricher/enricher MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 62 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 9 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.entityenricher/enricher
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.entityenricher/enricher?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
62 tools on 2026-11-18:
ack_database_deltasadd_schema_propertyadd_semantic_conceptanalyze_sampleanalyze_schemaanswer_job_questionanswer_llm_requestask_supportassign_sync_hostcancel_jobclassify_database_modelcreate_benchmark_scenariocreate_database_synccreate_schema_from_sampledelete_attachmentdelete_benchmark_scenariodelete_database_syncdelete_schemadelete_semantic_conceptsenrich_entityfetch_database_deltasgenerate_sampleget_benchmark_scenarioget_benchmark_scenario_resultsget_database_setup_instructionsget_enum_candidatesget_job_statusget_recordget_schemaget_schema_partget_semantic_conceptget_statsget_support_conversationimport_semantic_conceptslist_benchmark_scenarioslist_database_syncslist_entity_stateslist_modelslist_recordslist_schemaslist_semantic_conceptslist_support_conversationsmerge_recordsmerge_semantic_conceptsmigrate_semantic_embeddingsmove_schema_propertynest_schema_regionprobe_semantic_conceptpublish_schemaresolve_unify_proposalretry_expertisesrevert_benchmark_reference_updatesrun_benchmarksave_schemaset_benchmark_referencestart_batch_enrichmentsync_records_to_databaseupdate_benchmark_scenarioupdate_concept_aliasupdate_schemaupdate_schema_propertyupload_attachment
MCP Registry declaration
- Registry name:
ai.entityenricher/enricher - Declared version: 2.0.0
- Status: active
- Declared hosts:
entityenricher.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.entityenricher/enricher", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.entityenricher/enricher?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).