# noticed developer resources

noticed exposes one supported agent integration surface: a hosted Model Context Protocol server. It is intended for assistants and agents acting for an authenticated noticed user. Clients should use MCP so tool schemas, safety annotations, authorization, and resource discovery remain consistent.

## MCP endpoint

- Name: noticed
- Transport: Streamable HTTP
- URL: https://mcp.noticed.so/api/mcp
- Server Card: https://www.noticed.so/.well-known/mcp/server-card.json
- Protected-resource metadata: https://mcp.noticed.so/.well-known/oauth-protected-resource

Clients can send `initialize`, `tools/list`, `resources/list`, and reads of the server's public documentation resources without a credential. Tool calls and any access to a user's noticed data require authentication. Public listing exists only to make the interface inspectable; it never returns a user's network, notes, contact details, or account state.

## Authentication and least privilege

The preferred flow is OAuth 2.1 Authorization Code with PKCE S256. noticed publishes RFC 8414 metadata at https://www.noticed.so/.well-known/oauth-authorization-server and supports RFC 7591 dynamic client registration at https://www.noticed.so/api/oauth/register. The MCP origin publishes RFC 9728 protected-resource metadata and returns a `WWW-Authenticate` challenge that points clients to it.

The current delegated scope is `network:read`. It authorizes the connected noticed MCP surface for one signed-in user's tenant. Tenant isolation and tool-level safety annotations still apply, and clients should request no scope beyond the one declared by the protected resource. Personal noticed access keys are an alternative bearer credential for clients that do not support OAuth; signed-in users create and revoke them themselves at https://www.noticed.so/settings/api-keys.

## Connect an agent

1. Configure an MCP connection to https://mcp.noticed.so/api/mcp.
2. Follow the OAuth metadata and PKCE flow, or create a personal noticed access key in settings.
3. Call `account_status` to confirm the authenticated context.
4. Inspect tool annotations before acting. Read-only tools declare read-only behavior; writes remain explicit and tenant-scoped.
5. Start with `search_people`, `get_person`, or `network_summary` for retrieval. Use write tools only when the user has asked to save or change something.

## Access and testing

noticed is currently a private beta with self-serve sign-in for invited users. Personal access keys are self-serve after sign-in. The public discovery mode can be used to validate MCP transport, tool schemas, resources, OAuth metadata, and Server Card wiring without touching production user data. noticed does not currently claim a separate data sandbox or an always-available free tier; do not infer either from discovery access.

## Support

For integration questions, email contact@noticed.so. Public product, privacy, and security references are linked from https://www.noticed.so/llms.txt and https://www.noticed.so/sitemap.xml.