Nexbidofficial
A
licenseNot graded
qualityD
maintenanceAgentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).
MIT
FinCore Agentic Commerce
Server Details
Agentic commerce with 58 MCP tools for product search, checkout, A2A negotiation, C-Suite analytics.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
7 tool updates
- Added
batch_get_products - Added
compare_price - Added
get_inventory - Changed
get_product2 fields changed- changed
Input schema / properties / store_id / descriptionPrevious value: -"Store ID from search_products results — identifies which store to query"New value: +"Store ID from search_products results" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "currency": { + "type": "string" + }, + "in_stock": { + "type": "boolean" + }, + "price": { + "type": "number" + }, + "product_id": { + "type": "string" + }, + "product_url": { + "type": "string" + }, + "sale_price": { + "type": "number" + }, + "store_name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "type": "object" +}
- Added
query_coupon - Changed
search_products3 fields changed- changed
Input schema / properties / category / descriptionPrevious value: -"Filter by product category (e.g. \"electronics\", \"clothing\", \"home\")"New value: +"Filter by product category" - changed
Input schema / properties / query / descriptionPrevious value: -"What product to search for. Be specific — include brand, features, or use case (e.g. \"Sony noise-canceling headphones under $200\" or \"lightweight running shoes for marathon training\")"New value: +"What product to search for. Be specific." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "query": { + "description": "The search query used", + "type": "string" + }, + "results": { + "description": "Array of product results", + "type": "array" + }, + "total": { + "description": "Total number of results", + "type": "integer" + } + }, + "type": "object" +}
- Changed
trending_products1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "rankings": { + "description": "Array of trending products ranked by search volume", + "type": "array" + } + }, + "type": "object" +}
3 tool updates
- Changed
get_product4 fields changed- changed
Input schema / properties / product_id / descriptionPrevious value: -"Product ID"New value: +"Product ID from search_products results" - changed
Input schema / properties / product_id / typePrevious value: -"integer"New value: +"string" - added
Input schema / properties / store_idAdded value: +{ + "description": "Store ID from search_products results — identifies which store to query", + "type": "integer" +} - changed
Input schema / requiredPrevious value: -[ - "product_id" -]New value: +[ + "product_id", + "store_id" +]
- Changed
search_products4 fields changed- added
Input schema / properties / categoryAdded value: +{ + "description": "Filter by product category (e.g. \"electronics\", \"clothing\", \"home\")", + "type": "string" +} - added
Input schema / properties / limitAdded value: +{ + "description": "Max results (default 10, max 50)", + "type": "integer" +} - added
Input schema / properties / max_priceAdded value: +{ + "description": "Maximum price filter in USD", + "type": "number" +} - changed
Input schema / properties / query / descriptionPrevious value: -"Search keyword"New value: +"What product to search for. Be specific — include brand, features, or use case (e.g. \"Sony noise-canceling headphones under $200\" or \"lightweight running shoes for marathon training\")"
- Added
trending_products
2 tool updates
- First observed
get_product - First observed
search_products
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Agent Commerce MCP — agent-native A2A storefront. Discovery, Stripe checkout, affiliate program.
Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.
100+ MCP tools for AI agents: content metadata, trade intelligence, business-expertise analysis.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents and humans to search products across multiple stores, compare prices, and place real orders directly from the terminal using 46 MCP tools.872MIT
- AlicenseDqualityDmaintenanceEnables natural-language control of e-commerce operations including product management, order processing, inventory tracking, customer service, content generation, and advertising analytics through 15 integrated MCP tools. Provides a local-first commerce automation solution with SQLite storage and extensible channel adapters for end-to-end online store workflows.153MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform e-commerce operations through a standardized interface implementing the x402 and Agentic Commerce Protocol (ACP). Supports merchant sessions, product search, and payment orchestration with production-ready security features.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: batch vs single product query, price comparison, inventory status, coupon lookup, product search, and trending. Overlaps (e.g., get_product and get_inventory both involve inventory) are minimal and well-justified by different granularities.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: batch_get, compare, get, get, query, search, trending. No mixing of styles or ambiguous verbs.
Tool Count5/5
7 tools is well-scoped for an e-commerce information retrieval server. It covers core operations (search, detail, price, inventory, coupons, trending) without being too few or too many.
Completeness3/5
The tool set is strong on querying but lacks any transactional actions (e.g., add to cart, purchase, manage orders). For a full commerce agent, this is a notable gap. However, it covers the stated 'query and compare' domain adequately.