EmojiHub MCP — wraps EmojiHub API (free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 34 tools
Several clusters genuinely overlap: ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta (explicitly identical to the stable router), and deep_research all serve the same 'query the data' purpose, and entity_profile/compare_entities/recent_changes/resolve_entity blur together around company data. The polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) is distinguishable but requires reading dense descriptions to pick correctly. The verbose per-tool descriptions help selection but don't eliminate misselection risk.
Everything is snake_case, but verb conventions are mixed: verb_noun forms (list_subscriptions, resolve_entity, validate_claim) coexist with noun-first forms (entity_profile, recent_changes, recent_alerts, bet_research) and question-style names (ask_pipeworx). Readable and largely predictable, but not a single consistent pattern.
34 tools is heavy (above the 25+ 'too many' band), though the scope—a universal data-routing gateway plus memory, subscription, and emoji utilities—partly justifies the breadth. Redundancy exists (a beta router that duplicates the stable one), so not every tool clearly earns its place.
The gateway surface is well-covered: query, discovery, entity resolution, grounding, memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/alerts), feedback, and validation. Minor gaps: emoji coverage is thin (category/group/random only, no search-by-name or lookup-by-character), and no explicit update tool for stored memories.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."resolve_entity1 field changedInput schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."emoji-oracle MCP — wraps StupidAPIs (keyless — no credential needed)
Iconify MCP — wraps the Iconify public API (free, no auth)
Fruityvice MCP — wraps Fruityvice API (free, no auth)
Add one secure layer between your agents and this server.