# The2410 Projects

> Plan custom software with The2410: fit check, budget, timeline, inquiry and consultation booking.

- name: com.the2410/projects
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 87/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.the2410%2Fprojects
- tools: https://api.protogrid.dev/v1/servers/com.the2410%2Fprojects/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "projects": {
      "type": "http",
      "url": "https://projects.the2410.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 98
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-96% +updated-6d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 87/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: analyze-request-tool (idempotentHint); find_case_studies (idempotentHint); check_delivery_window (idempotentHint); …
- pass `tools.token_cost`: about 2,709 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 2,709 tokens to load them all
- tool set hash: abe7c6d73c166ac74be668f8fa7ef464
- badge: [![protogrid quality](https://protogrid.dev/badge/com.the2410/projects.svg)](https://protogrid.dev/servers/com.the2410/projects)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://projects.the2410.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.96153843)

## Packages

_none_

## Tools (9)

- `analyze-request-tool`: Evaluates whether The2410 can build the custom software project a customer describes. Use it when a customer describes a new project or request. Returns fit, relevant services or solutions, indicative pricing, a project_context_id and next_actions for the project tools. If the request is only a small task, returns route = small_task and the URL of the separate Human Tasks by The2410 connector. This is not a detailed project plan or a contractual estimate.
- `book_consultation`: Register a consultation with The2410 by sending an email to the team. Use this tool after the user selects a slot from the latest get_consultation_slots response and confirms that they want to book it. Provide the customer's name and email. The consultation language is English. The team will send the customer a separate confirmation with the meeting details. Do not submit the same booking again after a successful response.
- `check_delivery_window`: Check The2410's indicative delivery availability for the customer's software project. Use this tool when the user wants to know when The2410 could start the project and the approximate delivery window. The tool uses the current project context, estimated business days, and the customer's preferred start. Returned dates are indicative and are not a contractual commitment.
- `find_case_studies`: Find published The2410 case studies relevant to the customer's current software project. Use this tool when the user wants examples of similar work or relevant project experience. The tool uses the existing project context and returns up to five case studies, ordered by relevance. It does not change the project context, plan, or estimate.
- `get_consultation_slots`: Get available consultation times with The2410 for the current software project. Use this tool when the user wants to speak with The2410 or choose a consultation time. The tool retrieves current calendar availability and returns up to ten slots, ordered from earliest to latest, in the requested timezone. This tool does not reserve a slot or create a booking.
- `plan-project-tool`: Create a preliminary project plan, price range and development effort estimate. Use this tool to understand the main functional modules and important unresolved requirements. Provide an existing project_context_id or a project_description for a new project. Module status describes The2410's proposed solution; confirmed does not mean customer approval. Prices and working days are shares of the existing project estimate. This is a preliminary estimate, not a final specification or contractual offer.The customer's name and email are required; phone and company name are optional.
- `prepare-project-inquiry-tool`: Prepare a project inquiry for review before submission to The2410. Run plan-project-tool first and provide the existing project_context_id. The customer's name and email are required on every call; company and phone are optional. Return the saved project fit, offering, estimate and modules with their price and effort. Delivery dates are indicative; if not calculated, the response explains how to request them. This tool does not submit the inquiry or send an email.
- `send-feedback-tool`: Send feedback to The2410 team: a problem, a suggestion, praise or any other message about this MCP server, an order or a project. Use only when the customer wants to share feedback. Show the message to the customer and send it after they confirm. Name and email are optional; include them if the customer wants a reply. If the feedback is about a specific project or order, add the project_context_id or order_id returned by an earlier call. Never include passwords, access details or payment card data.
- `submit-project-inquiry-tool`: Submit the customer's project inquiry to The2410 by email. Use this tool after the customer has reviewed the inquiry and explicitly asked to submit it. Provide the existing project_context_id and the reviewed contact details. Name and email are required; company and phone are optional. The tool uses the saved analysis and plan, then emails the inquiry to The2410. It does not send an automatic confirmation email to the customer. Do not repeat this call after a successful submission.