Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add a PropertyListRef resolver (MCP get_property_list, auth_token bearer, pagination, cache_valid_until)

Open
  • Is something wrong?
#576 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go, typescript
Domain
backend-api-design, networking, security

Research direction

Start with the existing PropertyListRef type and TypeScript resolvePropertyList, then trace adcp/v3/internal/safefetch and the MCP client’s request/authentication patterns. Implement ResolvePropertyList(ctx, ref) around those entry points, covering bearer auth, complete pagination, returned identifiers, cache_valid_until, optional caching, and SSRF protection. Done means Go sellers can resolve every supported property-list reference consistently with the TypeScript SDK, with focused tests for pagination, cache expiry, auth, and unsafe URLs.

Written by the indexing model from the issue text.

Description

Problem

PropertyListRef{AgentURL, ListID, AuthToken} is a type only. Nothing in the SDK resolves a reference, so every Go seller that receives a property list (in targeting_overlay.property_list, property_list_exclude or criteria.offer_filters.property_list) writes its own fetcher. Each one guesses the transport, auth, paging and caching.

Ask

A ResolvePropertyList(ctx, ref) helper that:

  • calls the MCP tool get_property_list at AgentURL, with AuthToken as the bearer token;
  • follows pagination to the end;
  • returns identifiers plus cache_valid_until, with an optional cache honouring it;
  • goes through adcp/v3/internal/safefetch for SSRF protection.

This should match the TypeScript SDK's resolvePropertyList, so Go and TypeScript sellers read lists the same way. The spec doesn't yet say how a reference is fetched; adcontextprotocol/adcp#8282 asks it to.

Dominant language
Go
Stars
4
Forks
2
Avg merge
17h
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adcontextprotocol/adcp-go

All issues in adcontextprotocol/adcp-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.