NamSor for AI agents
NamSor classifies and enriches personal names to infer likely gender, country of origin, and cultural background for segmentation and personalization. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in NamSor.
Infer a name's likely origin
Classify a contact's name to infer likely country of origin for market segmentation.
Parse a full name into parts
Parse a raw name string into first and last name fields for a data cleanup task.
Check usage, read-only
Look up API usage before running a large batch of name classifications, a read-only check that changes no data.
7 NamSor actions, graded by risk.
Every NamSor action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- namsor.get_account_usageGet Account Usage
- namsor.parse_namesParse Personal Names
write
5Create and change things. Allow, or ask the user first.
- namsor.classify_genderClassify Name Gender
- namsor.classify_originClassify Name Origin
- namsor.classify_diasporaClassify Name Diaspora
- namsor.classify_proper_noun_typeClassify Proper-Noun Type
- namsor.classify_residence_countryClassify Residence Country
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
NamSor in three steps.
- 01Your users connect NamSorThey add their NamSor api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “classify Name Gender” can wait for the user to approve.
- 03Any agent can actYour agent calls NamSor through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('namsor', { read: 'allow', write: 'ask', // classify_gender destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How NamSor connects.
Users add their NamSor api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same NamSor connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use NamSor from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
NamSor and Arc0, answered.
Can I use NamSor with Claude, ChatGPT or Cursor?
Yes. Connect NamSor to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the NamSor actions you allow.
How do users connect NamSor?
Users add their NamSor api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which NamSor actions can my agent take?
7 in total: 2 read, 5 write and 0 destructive, such as “classify Name Gender”. Your policies decide which of them each agent may call.
Can I make my agent read-only in NamSor?
Yes. Allow read actions and deny writes in the NamSor policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call NamSor too?
Yes. The same NamSor connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug NamSor into your agent.
Your users connect NamSor once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan