iquesta-mcp
Registry code: 649fb38f1916c294
Recherche d'offres de stage et d'alternance en France via le réseau iQuesta.com
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.iquesta.com/api/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is iquesta-mcp live?
- Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
- Is iquesta-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does iquesta-mcp have?
- 3 tools: get_job, search_jobs, list_filters.
- Is iquesta-mcp 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.
90 days 99.4%· all time 99.4%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- search internships and apprenticeships in france
- get job offer details
- list search filter values
- takes → gives
- text → data
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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.
list_filters reads open 7h ago
Liste les valeurs possibles pour les filtres de recherche (disciplines, régions, types de contrat). À appeler avant search_jobs si l'utilisateur mentionne un secteur ou une région, pour convertir le nom en ID correct.
{ "type": "object", "required": [ "filter" ], "properties": { "filter": { "enum": [ "disciplines", "matieres", "regions", "contracts", "all" ], "type": "string", "description": "Quel filtre lister. 'all' retourne les quatre." } } }arguments 19 linesget_job reads unknown 7h ago
Récupère le détail complet d'une offre par son ID
{ "type": "object", "required": [ "job_id" ], "properties": { "job_id": { "type": "string", "description": "Identifiant de l'offre dans iQuesta" } } }arguments 12 linessearch_jobs reads unknown 7h ago
Recherche des offres de stage, alternance, emploi ou job étudiant sur iQuesta.com. Avant de lancer la recherche, demander à l'utilisateur quel type de contrat il recherche (stage, alternance, emploi, job étudiant) si ce n'est pas précisé dans sa demande. Pour filtrer par région, discipline ou type de contrat, appeler d'abord list_filters pour obtenir les IDs valides — ne jamais deviner un ID.
{ "type": "object", "required": [], "properties": { "term": { "type": "string", "description": "Mots-clés recherchés dans le titre de l'annonce (ex: 'développeur web', 'assistant marketing', 'ressources humaines')" }, "begin": { "type": "integer", "description": "Mois de début souhaité de la mission, de 1 (Janvier) à 12 (Décembre). Omettre si aucune contrainte de date." }, "limit": { "type": "integer", "default": 15, "description": "Nombre maximum de résultats à retourner (défaut: 15, max recommandé: 20)" }, "regions": { "type": "integer", "description": "ID de région française, obtenu via list_filters(filter='regions'). Exemple : 10 pour Ile de France, 6 pour Bretagne. Toujours vérifier la liste complète avant de choisir un ID, ne jamais deviner." }, "duration": { "type": "integer", "description": "Durée maximale de la mission en mois (ex: 3, 6, 12, 24). Omettre si aucune contrainte de durée." }, "matieres": { "type": "array", "items": { "type": "integer" }, "description": "Liste d'IDs de matières, obtenus via list_filters(filter='matieres'). Plus précis que 'disciplines' (ex: 'Développement web' plutôt que 'Informatique'). Toujours vérifier la liste complète avant de choisir un ID, ne jamais deviner." }, "contracts": { "type": "string", "description": "ID du type de contrat. Valeurs : '1' (Stage), '2' (Alternance), '-4' (Emploi), '-5' (Job étudiant). Toujours demander ce critère à l'utilisateur s'il ne l'a pas précisé — ne jamais omettre ce filtre." }, "description": { "type": "string", "description": "Mots-clés recherchés dans le texte/descriptif complet de l'annonce (missions, compétences requises, etc.). À utiliser pour cibler des compétences ou détails précis absents du titre." }, "disciplines": { "type": "integer", "description": "ID de discipline, obtenu via list_filters(filter='disciplines'). Exemple : 9 pour Informatique, 5 pour Economie/Gestion/Commerce. Toujours vérifier la liste complète avant de choisir un ID, ne jamais deviner." } } }arguments 46 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id649fb38f1916c294.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/649fb38f1916c294/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/649fb38f1916c294?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.