_ registry / mcp http-sse · checked 1h ago

recommerce-chatgpt-app

https://mcp.recommerce.com

Registry code: 7290d42c1b0622cd

api record
endpoint
https://mcp.recommerce.com/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is recommerce-chatgpt-app live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is recommerce-chatgpt-app free to use?
Yes — the hub reached it with no key and no payment.
What tools does recommerce-chatgpt-app have?
3 tools: recommerce-faq, send_feedback, search-recommerce.
Is recommerce-chatgpt-app safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
5,102ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search-recommerce open 1h ago

    Search for products in the recommerce catalog. The catalog includes refurbished products: phones, tablets, laptops & games consoles.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "os": {
          "enum": [
            "-",
            "Android",
            "Horizon OS",
            "Orbis Os",
            "Prospero OS",
            "Xbox OS",
            "iOS",
            "iPadOS",
            "macOS"
          ],
          "type": "string",
          "description": "Product operating system, always in french"
        },
        "color": {
          "enum": [
            "Argent",
            "Blanc",
            "Bleu",
            "Gris",
            "Gris sidéral",
            "Jaune",
            "Marron",
            "Noir",
            "Noir de jais",
            "Or",
            "Orange",
            "Rose",
            "Rouge",
            "Vert",
            "Violet"
          ],
          "type": "string",
          "description": "Product color, always in french."
        },
        "grade": {
          "enum": [
            "Bon état",
            "Etat correct",
            "Etat parfait",
            "Très bon état"
          ],
          "type": "string",
          "description": "Product grade, always in french"
        },
        "query": {
          "type": "string",
          "description": "Free text search on product title. Example: Iphone Pro, Galaxy S24, etc."
        },
        "brands": {
          "type": "array",
          "items": {
            "enum": [
              "Apple",
              "Google",
              "Honor",
              "Huawei",
              "Microsoft",
              "Nintendo",
              "OnePlus",
              "Oppo",
              "Samsung",
              "Sony",
              "Xiaomi"
            ],
            "type": "string"
          },
          "description": "Product brands to filter by (OR logic), always in english. Example: ['Apple', 'Samsung']"
        },
        "models": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Product models to search for (OR logic), always in english. Do not include the brand name in the model name. This filter is very important to use. Example: ['iPhone 15 Pro', 'iPhone 14 Pro'] or ['Galaxy S24', 'Galaxy S23']"
        },
        "sortBy": {
          "enum": [
            "price-asc",
            "price-desc",
            "grade-asc",
            "grade-desc"
          ],
          "type": "string",
          "description": "Sort the results by price or grade, ascending or descending. Default is grade-desc (best grade first)."
        },
        "capacity": {
          "type": "object",
          "properties": {
            "max": {
              "type": "number",
              "description": "Maximum capacity, in GB"
            },
            "min": {
              "type": "number",
              "description": "Minimum capacity, in GB"
            }
          },
          "description": "Product capacity, in GB"
        },
        "screenSize": {
          "type": "object",
          "properties": {
            "max": {
              "type": "number",
              "description": "Maximum screen size, in inches"
            },
            "min": {
              "type": "number",
              "description": "Minimum screen size, in inches"
            }
          },
          "description": "Product screen size, in inches"
        },
        "user_intent": {
          "type": "string",
          "description": "A concise summary of what the user is trying to accomplish, derived from their message or the\nconversation context that triggered this tool call.\nThis is used to understand the user's intent and context to improve the overall user experience.\n\n- For short, self-contained prompts (e.g. \"I want new shoes\"), copy the user message as-is.\n- For longer conversations or detailed requests, summarize the core goal and any relevant\n  context in 1-2 sentences. Focus on intent, constraints, and preferences - not the full\n  dialogue.\n\nBefore sending, strip all personally identifiable information (PII), including but not\nlimited to:\n  - Names (first, last, usernames, handles)\n  - Email addresses\n  - Phone numbers\n  - Physical addresses (street, city, zip/postal code, country when tied to an individual)\n  - Dates of birth or exact ages\n  - Government-issued ID numbers (SSN, passport, driver's license, etc.)\n  - Payment or financial information (card numbers, bank accounts, etc.)\n  - IP addresses or device identifiers\n  - Account credentials (passwords, tokens, API keys)\n  - Health or biometric data\n  - Any other information that could identify a specific individual\n\nReplace stripped values with a generic placeholder (e.g. \"[name]\", \"[email]\", \"[address]\").\n\nExamples:\n  User: \"I want red running shoes under $100\"\n  -> \"I want red running shoes under $100\"\n\n  User: \"Hi, I'm John Smith, [email protected], and I'm looking for flights from Paris to\n         Tokyo for 2 adults departing around mid-June, budget around EUR2000 total\"\n  -> \"Looking for flights from Paris to Tokyo for 2 adults, mid-June, budget ~EUR2000\"\n\n  User: \"I need help resetting my password for account ID acct_12345\"\n  -> \"I need help resetting my password for account ID [account_id]\""
        }
      }
    }
    arguments 125 lines
  • recommerce-faq unknown 1h ago

    Answer frequently asked questions about Recommerce. Available themes: - refurbishedProduct: What is a refurbished product - deliveryOptions: Delivery options, costs and delays - warranty: Warranty information (36 months) - cosmeticGrades: Cosmetic grades explanation (100% functional, different appearances) - whyRefurbished: Why buy refurbished (ecological, affordable, 60 quality checks) - technicalSpecifications: Where to find technical specifications - accessories: Accessories info (included kit, optional purchases)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "theme"
      ],
      "properties": {
        "theme": {
          "enum": [
            "refurbishedProduct",
            "deliveryOptions",
            "warranty",
            "cosmeticGrades",
            "whyRefurbished",
            "technicalSpecifications",
            "accessories"
          ],
          "type": "string",
          "description": "The FAQ theme to get information about."
        },
        "user_intent": {
          "type": "string",
          "description": "A concise summary of what the user is trying to accomplish, derived from their message or the\nconversation context that triggered this tool call.\nThis is used to understand the user's intent and context to improve the overall user experience.\n\n- For short, self-contained prompts (e.g. \"I want new shoes\"), copy the user message as-is.\n- For longer conversations or detailed requests, summarize the core goal and any relevant\n  context in 1-2 sentences. Focus on intent, constraints, and preferences - not the full\n  dialogue.\n\nBefore sending, strip all personally identifiable information (PII), including but not\nlimited to:\n  - Names (first, last, usernames, handles)\n  - Email addresses\n  - Phone numbers\n  - Physical addresses (street, city, zip/postal code, country when tied to an individual)\n  - Dates of birth or exact ages\n  - Government-issued ID numbers (SSN, passport, driver's license, etc.)\n  - Payment or financial information (card numbers, bank accounts, etc.)\n  - IP addresses or device identifiers\n  - Account credentials (passwords, tokens, API keys)\n  - Health or biometric data\n  - Any other information that could identify a specific individual\n\nReplace stripped values with a generic placeholder (e.g. \"[name]\", \"[email]\", \"[address]\").\n\nExamples:\n  User: \"I want red running shoes under $100\"\n  -> \"I want red running shoes under $100\"\n\n  User: \"Hi, I'm John Smith, [email protected], and I'm looking for flights from Paris to\n         Tokyo for 2 adults departing around mid-June, budget around EUR2000 total\"\n  -> \"Looking for flights from Paris to Tokyo for 2 adults, mid-June, budget ~EUR2000\"\n\n  User: \"I need help resetting my password for account ID acct_12345\"\n  -> \"I need help resetting my password for account ID [account_id]\""
        }
      }
    }
    arguments 26 lines
  • send_feedback unknown never probed

    Send feedback about this MCP server to its operators. Use this tool ONLY for feedback about this MCP server itself, never about other tools, services, or the host. You MAY call this tool when you detect a genuine issue with this server (e.g. a tool that failed unexpectedly, an unhelpful response, a missing capability). You MAY also call it when the user explicitly asks to send feedback. Before sending, strip all personally identifiable information (PII) from the content, including names, email addresses, phone numbers, physical addresses, dates of birth, ID numbers, payment information, and any other information that could identify a specific individual. Replace stripped values with generic placeholders (e.g. "[name]", "[email]").

    mcp-tool

    {
      "type": "object",
      "required": [
        "content",
        "source"
      ],
      "properties": {
        "source": {
          "enum": [
            "model",
            "user"
          ],
          "type": "string",
          "description": "Who initiated this feedback: \"user\" if the user explicitly asked to send feedback, \"model\" if you are sending it autonomously."
        },
        "content": {
          "type": "string",
          "description": "The feedback content, stripped of any Personally Identifiable Information (PII)."
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7290d42c1b0622cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7290d42c1b0622cd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7290d42c1b0622cd/badge.svg)](https://brick.blue/agent/7290d42c1b0622cd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.