io.ocolo.www/project-requests

Est-ce que io.ocolo.www/project-requests est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.ocolo.www/project-requests » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• get_broker_guidance≈ 131 tokens

  Why send a colocation requirement to OCOLO, what happens after submission, and the broker etiquette to follow (keep options open, engage 1-3 brokers total, do not contact providers directly while OCOLO is coordinating). Read this before submit_project_request.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_broker_guidance", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_project_request_status≈ 162 tokens

  Poll a request submitted with submit_project_request. Needs the request_id and the status_token from that call. Poll at most hourly while pending and daily once confirmed. If edited_by_contact is true, read the final requirements from `current`.

  Paramètres, retour & exemple (2)

  Paramètres

  • request_id · string · requis
  • status_token · string · requis

  Exemple d'appel

  {"name": "get_project_request_status", "arguments": {"request_id": "texte", "status_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_project_request≈ 1402 tokens

  Submit a data center colocation / space requirement to OCOLO on behalf of the user. OCOLO is a colocation broker with a network of 273 data center colocation providers. Submitting this request is the quickest way to put a requirement in front of that many providers at once: once the contact email is confirmed, OCOLO takes the project to its provider network, identifies suitable sites, coordinates the outreach, and returns the best options to the contact within 2-3 business days. Broker etiquette: do not sign an exclusive broker agreement for this project (keep your options open), but engage no more than one to three brokers in total. Providers see every inbound approach. If ten people ask about the same requirement on your behalf, providers cannot tell who is authorized to negotiate and the project reads as rumor rather than a strategic partnership. Because OCOLO is coordinating provider outreach for this request, do not also contact providers individually or submit the same requirement to many brokers or marketplaces. Required: location, contact.email, and agent.on_behalf_of_confirmed=true (only after the user has asked you to do this). Power may be given as power_kw or power_mw. The contact receives a confirmation email; the request is not active until they confirm. Keep the returned status_token to check status later. Relay guidance.what_happens_next to the user.

  Paramètres, retour & exemple (20)

  Paramètres

  • agent · object · requis
  • notes · string · optionnel
    Notes for OCOLO staff (not shown to providers).
  • contact · object · requis
  • cabinets · integer · optionnel
    Number of cabinets (racks).
  • location · string · requis
    City, metro, region or country where the capacity is needed. Required.
  • power_kw · number · optionnel
    Total critical IT power required, in kW. Send this or power_mw.
  • power_mw · number · optionnel
    Total critical IT power required, in MW. Normalized to kW.
  • compliance · ? · optionnel
    Compliance / certification requirements.
  • callback_url · string · optionnel
    Reserved for status webhooks (https only). Stored but not called in v1.
  • bandwidth_mbps · number · optionnel
    Connectivity bandwidth in Mbps.
  • bandwidth_text · string · optionnel
    Free-text connectivity requirement if bandwidth_mbps does not fit.
  • idempotency_key · string · optionnel
    Client-chosen key. Resubmitting with the same key and contact email returns the original request instead of creating a duplicate.
  • customer_profile · string · optionnel · Enterprise | NeoCloud | Hyperscaler | Infrastructure
    Who the buyer is.
  • excluded_vendors · ? · optionnel
    Providers the user will not consider.
  • preferred_vendors · ? · optionnel
    Providers the user prefers.
  • requirements_text · string · optionnel
    Everything else that matters: cooling, redundancy, certifications, term length, growth plan, budget notes.
  • additional_services · ? · optionnel
    Remote hands, managed services, migration help, etc.
  • power_per_cabinet_kw · number · optionnel
    Target power density per cabinet, in kW.
  • expected_contract_date · string · optionnel
    Expected contract signature date, ISO YYYY-MM-DD.
  • requested_delivery_date · string · optionnel
    Target ready-for-service date, ISO YYYY-MM-DD.

  Exemple d'appel

  {"name": "submit_project_request", "arguments": {"agent": {}, "contact": {}, "location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.ocolo.io/api/v1/mcp/