Skip to main content
Glama

Brand Intelligence MCP

by io.github.FoundryNet
OverviewDiscussionsAdmin

Server Details

Domain & brand intelligence: company enrichment, tech stack detection, brand research.

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.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
FoundryNet/brand-intel-mcp
GitHub Stars
0
Server Listing
Brand Intelligence MCP

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct purpose: bulk enrichment, brief summary, full daily brief, domain age, full profile, network info, and tech stack. No two tools overlap in functionality.

Naming Consistency4/5

All names use snake_case consistently, but not all follow a strict verb_noun pattern (e.g., 'brief_summary' and 'daily_brief' are noun-based). The pattern is predictable and readable.

Tool Count5/5

Seven tools cover the domain of brand intelligence efficiently, each addressing a specific need without redundancy. The count feels well-scoped for the server's purpose.

Completeness5/5

The toolset covers core operations: bulk enrichment, individual profiling, domain age, tech stack analysis, daily briefs, and network info. No obvious gaps for the stated domain.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • Changedbatch_enrich1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedbrief_summary1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changeddaily_brief2 fields changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402 (x402 rail)."New value: +"payment transaction reference, when re-calling after a 402."
      • changedInput schema / properties / stripe_token / description
        Previous value: -"Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."New value: +"Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative payment rail). Can also be\nsupplied via the X-Stripe-Token header."
    • Changeddomain_profile1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
    • Changedtech_stack1 field changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
  2. 1 tool update
    • Addedbrief_summary
  3. 1 tool update
    • Changeddaily_brief2 fields changed
      • changedInput schema / properties / payment_tx / description
        Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)."
      • addedInput schema / properties / stripe_token
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."
+}
  4. 1 tool update
    • Addedmint_info
  5. 1 tool update
    • Addeddaily_brief
  6. 4 tool updates
    • First observedbatch_enrich
    • First observeddomain_age
    • First observeddomain_profile
    • First observedtech_stack

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources