Atlas entry
www.aiprofile.com
4 capabilities over MCP. First atlas observation.
Surfaces
5 protocols checked
| ARD | Not found | No document retrieved |
|---|---|---|
| A2A | Not found | 0 skills |
| MCP | Valid | 2025-11-25 · 4 tools · resources not advertised · prompts not advertised |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDabsent
Exact state: not found · No document retrieved
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- A2Aabsent
Exact state: not found · 0 skills
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- MCPobserved
Exact state: valid · Revision 2025-11-25 · 4 tools · resources not advertised · prompts not advertised
A usable protocol document was retrieved and validated.
Directly observed
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
4 · inventory complete
Summary of the AI readings · beta
The service lists 4 capabilities, and 4 have AI readings.
4 capabilities are read as read-only, including search_business, ask_business and get_profile.
Rows named: search_business · ask_business · get_profile
Written by code from the AI readings on this page: it groups them and says nothing they do not.
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
MCP tools 4
ask_businessinputs
business_id(required),language,question(required)AI Reads only 0.90
discover_businessesinputs
category(required),city(required),country(required),languageand 2 moreAI Reads only 0.90
get_profileinputs
business_id(required),languageAI Reads only 0.92
search_businessinputs
language,limit,query(required)AI Reads only 0.85
Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.
Declared and observed
4 tools declare hints; the AI readings agree with all 4 that have a reading.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 4 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
ba41db40e2396b8602da9829c96a853b4a69fd4243f8b528264b253ef59a9d31- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
About this entry
com.aiprofile/answersListedOfficial MCP Registry · first listed 2 Nov 2026 · last listed 2 Nov 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:9a9ce24ec43cd5f7b3204aa47e7589cc0b984e9f107f98841f33477cc52e0dfe- Locator SHA-256
160979b43b604e46bfe8b9779e175b4bd16dc349150c9dcdeb1ff5220e8a60d0- Snapshot generated
- 4 Nov 2026, 00:59 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

