# noticed developer resources
Connect an agent through the hosted noticed Model Context Protocol server, with scoped OAuth.
## Synthetic sandbox
Try noticed without an account, payment method, production credential, or user data. Send `POST` to [https://mcp.noticed.so/api/sandbox/session](https://mcp.noticed.so/api/sandbox/session) to create a 30-minute handle, then use its Authorization header with [https://mcp.noticed.so/api/sandbox/mcp](https://mcp.noticed.so/api/sandbox/mcp). Creating another handle resets the session.
This MCP server is isolated from the production capability client and contains fixed fictional people only. Its complete surface is the read-only `search_people`, `get_person`, and `network_summary` tools. The handle carries only `sandbox:read` and expires automatically.
## Open-source agent resources
Inspect the public noticed implementations and reusable agent workflows directly at their canonical repositories.
- [noticed CLI and MCP source](https://github.com/noticedso/cli): Public source for the noticed CLI and MCP server
- [noticed agent labs](https://github.com/noticedso/noticed-labs): Public agent-evaluation and query-optimization skills
- [noticed relationships extension](https://github.com/noticedso/relationships-extension): Public browser-extension source for private LinkedIn imports
## Model Context Protocol
MCP is the supported noticed integration surface. Connect using Streamable HTTP at [https://mcp.noticed.so/api/mcp](https://mcp.noticed.so/api/mcp). Clients can initialize and list public tool schemas and documentation resources without credentials. Every tool call that can reach a user's relationship data remains authenticated.
- [noticed MCP Server Card](/.well-known/mcp/server-card.json)
- [noticed MCP compatibility catalog](/.well-known/mcp/catalog.json)
- [OAuth protected-resource metadata](https://mcp.noticed.so/.well-known/oauth-protected-resource)
- [noticed AI catalog](/.well-known/ai-catalog.json)
## Authentication and scoped permission
noticed supports OAuth 2.1 Authorization Code with PKCE S256 and RFC 7591 dynamic client registration. The delegated scope is `network:read`. OAuth tokens are audience-bound to the MCP resource, and user data remains subject to tenant, membership, consent, and tool-level authorization checks.
## Connect safely
1. Configure an MCP client with the Streamable HTTP URL above.
2. Follow OAuth discovery and PKCE, or supply a noticed access key.
3. Call account\_status to confirm the authenticated context.
4. Inspect tool safety annotations and start with read-oriented tools.
5. Use write tools only when the user explicitly asks for a change.
noticed is currently available through early access. Integration support is available at [contact@noticed.so](mailto:contact@noticed.so).
[Full developer context](/developers/llms.txt) · [Authentication guide](/auth.md)